GET /workflows/tasks
Retrieves a list of workflow tasks available in your Zuora tenant.
User Access Permission
You must be assigned the Workflow View Access permission to run this operation.
Servers
- https://rest.test.zuora.com
- https://rest.sandbox.na.zuora.com
- https://rest.apisandbox.zuora.com
- https://rest.na.zuora.com
- https://rest.zuora.com
- https://rest.test.eu.zuora.com
- https://rest.sandbox.eu.zuora.com
- https://rest.eu.zuora.com
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Encoding |
String | No |
Include the |
Zuora-Track-Id |
String | No |
A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue. The value of this field must use the US-ASCII character set and must not include any of the following characters: colon ( |
Authorization |
String | Yes |
The value is in the |
Zuora-Entity-Ids |
String | No |
An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you do not need to set this header. |
Zuora-Org-Ids |
String | No |
Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header. The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails. If the header is not set, the operation is performed in scope of the user's accessible orgs. |
Accept-Encoding |
String | No |
Include the If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a |
Query parameters
Name | Type | Required | Description |
---|---|---|---|
id |
String | No |
If specified, the operation retrieves the task that is with specified id. |
page |
Integer | No |
If you want to retrieve only the workflows on a specific page, you can specify the Default value: 1 |
name |
String | No |
If specified, the operation retrieves tasks that is in the specified name. |
object |
String | No |
If specified, the operation retrieves tasks with the specified object. |
page_length |
Integer | No |
The number of workflow tasks shown in a single call. If the Default value: 20 |
object_id |
String | No |
If specified, the operation retrieves tasks with the specified object id. |
call_type |
String | No |
If specified, the operation retrieves tasks with the specified api call type used. |
tags[] |
Array | No |
If specified, the operation retrieves tasks that with the specified filter tags. Use the following syntax to specify multiple tags: Note: All the workflow tasks that have any of the specified tags will be listed in the response body. |
workflow_id |
String | No |
If specified, the operation retrieves tasks that for the specified workflow id. |
instance |
Boolean | No |
If set to true, the operation retrieves workflows that have the scheduled trigger enabled. If set to false, the operation retrieves workflows that have the scheduled trigger disabled. If not specfied, the operation will not use this filter. |
action_type |
String | No |
If specified, the operation retrieves tasks that is the specified type. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.