Workflow triggers are enabled by WebHooks. The ability to use a trigger for your desired service is dependent only on if that service has a WebHook.
What is a WebHook?
If a WebHook is available, it means that your service sends out a signal based on certain actions that occur internally. WebHooks are a modern concept... due to this, not all services provide WebHooks with their API, but the list of those that do increases daily. Some example 'actions' that catalyze a WebHook signal are:
<Contact created>, <Contact updated>, <Lead created>, <Lead updated>
See if your service is in the list... if it isn't, skip to Utility Triggers.
These are mainly used for integrating with services that do not have a WebHook. We'll go through them one-by-one.
To re-iterate, WebHooks send out a signal based on certain events that occur within your chosen system. If there is no WebHook associated with your system, you will need to use a ' Scheduled Input' trigger.
This is used for passing data between multiple workflows. When used in combination with the 'Call Workflow' connector, data from one flow may be passed to any other. When the Callable Trigger receives a notification from a 'Call Workflow' connector, your workflow will activate.
Tray allows you to create custom forms, and trigger your workflows with their submission. All data entered into the form can be passed to any service you wish to integrate with. This is a powerful data-entry tool that has countless applications.
This trigger is great for testing your workflow. When enabled, clicking 'Run Workflow' will run a single instance of your flow, executing all connectors.
Pro Tip: Create a new workflow with a single connector to test the output of a specific operation for a given service. Why this is useful.
We use this trigger to grab data from the service of your choice in time-intervals. Since the service does not inherently tell us that data has been changed or updated through a WebHook, we have to poll (request data) from the service and manually check for data additions and updates.
Many services that Tray has not yet built an in-house integration for may be accessed by a normal HTTP request. Tray provides you with a public URL that can receive WebHook calls from any external system. See: Triggers - Webhook.
>>> Next: Authenticate your Workflow >>>