# Service tasks

Service tasks are essential components of every workflow template. They define the actions available in the BPMN designer and drawn in the workflow template.&#x20;

Service tasks can be either **standard** or **triggerable**.

* **Standard service tasks** execute and complete the action they are called to perform, and then the workflow continues. An example of standard service task is the RenameFile service task that executes and completes the rename task. See the [Standard service tasks](/data-mover-1.21/workflow-templates/service-tasks/standard-service-tasks.md) page for a description of these service tasks.&#x20;
* **Triggerable service tasks** do not perform a specific action, but rather, initiate a request to start an operation. The instance enters a paused state, waiting for a completion notification to trigger it. The spPush service task, for example, delivers a file to a remote host using a specific protocol. It sends a request to STENG to initiate the file transfer and then waits. Once the transfer finishes, the process is triggered again upon receiving the completion event.  They are documented on the [Triggerable service tasks](/data-mover-1.21/workflow-templates/service-tasks/triggerable-service-tasks.md) page.&#x20;

**Primeur can offer additional Service tasks with a separate license.**

The description of how to use service tasks to create workflow templates is on the [Create a user-designed workflow template](/data-mover-1.21/workflow-templates/user-designed-workflow-templates.md) page and on its subpages.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.primeur.com/data-mover-1.21/workflow-templates/service-tasks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
