Triggers

Modified on Tue, 30 Jan, 2024 at 3:46 PM

Every workflow commences with a trigger activity, which is executed in response to an external event. These events can take one of the following forms:

  1. A Heed response submitted by recipients.
  2. The expiration of a timed schedule.
  3. An event originating from an external application.


The choice of trigger for a workflow is determined during its creation and remains fixed thereafter.


Scopes

Each trigger associated with an application integration is directly linked to the application's connection, configured in the "Integration Connections" section. When creating a workflow triggered by an application, it is essential to select the relevant associated connection.


Should you require multiple workflows, each one will activate when data is received from the application. This may impact execution performance, especially with a large number of workflows, and can complicate each workflow as you'd need to implement filters at their outset to determine their activation criteria. To mitigate this, you can apply scopes to your workflows, ensuring that the application triggers only the relevant workflows for the specific event.


For instance, suppose you have multiple workflows processing events from a change management application, where events could be either "change tasks" or "change approvals." You could apply the "change-approval" scope to all change approval workflows and "change-tasks" to the change task workflows. With this setup, a workflow with the "change-approval" scope would be triggered via the following URL:


https://app.heed.io/api/v2/alerts/send/app?scope=change-approval


Workflows without the specified scope in the URL would not be triggered. It's important to note that if you apply scopes to some workflows but not others, the absence of a scope in the triggering URL will still trigger all workflows.


Adding a scope to your workflow is a straightforward process:

  1. Open an existing application integration workflow or create a new one.
  2. Select the trigger, then click the Add button under Scopes.


  3. Enter your desired scope and click Save.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article