While viewing the Template, Process or Task in a browser...

When using TeamworkIQ in your web browser you'll notice that each Template, Process or Task has a unique URL.

For Processes the URL looks like this:
https://app.teamworkiq.com/#/processes/1234/6789?taskNo=5005

For Templates the URL looks like this:
https://app.teamworkiq.com/#/templates/1234/876?taskNo=5005

In each of the examples above the Account Number is 1234.

In the Template example above, the Template Number is 876. Thus templates/1234/876 means template 876 in account 1234.

In the Process example above, the Process Number is 6789. Thus processes/1234/6789 means process 6789 in account 1234.

In each of the examples the Task Number is 5005 within its respective template or process and account.

When using the TeamworkIQ App for Zapier...

When you use any of the TeamworkIQ App for Zapier's triggers to start a new automated Zap in Zapier, the data provided by the trigger includes the Process Number and Template Number and, in most cases, the Task Number. Look for 'process_no', 'template_no' and 'task_no' in the trigger's response data.

Some TeamworkIQ App for Zapier Actions require Template Number, Process Number, and Task Number as input. You can map the data output from the trigger into the inputs for the actions if you goal is to have an event from a process cause other parts of the same process to be updated.

When using the TeamworkIQ API...

When using the TeamworkIQ API, API endpoints have a similar structure to the URLs used to view Templates, Processes and Tasks. Learn more.

Did this answer your question?