Triggers
Last updated
Last updated
A Trigger is the initial step that activates your workflow in MESA. There are various types of triggers you can utilize, each initiating workflows based on different criteria.
We'll go through the difference between each type of trigger and how to identify if your trigger is an event-based trigger or a polling trigger.
Every workflow begins with a Trigger, the spark that gets everything rolling. Here’s a rundown of the various trigger types you can play with in MESA.
These triggers kickstart your workflow in response to specific events. For instance, when a Shopify order is created, the corresponding workflow runs immediately. Event-based triggers allow for real-time processing for your automation without waiting for scheduled times.
Event-Based Triggers are like the prompts that kickstart your workflows based on specific activities or actions happening.
Certain Triggers use/offer a polling system to initiate the workflow at specific time intervals. Depending on the Trigger, you may be able to select the polling interval or it may be native to the third-party service's data send. Whoa - that's technical, so what does that mean? Every hour, or whatever frequency the polling is set at, MESA will look for any recent activity associated with the trigger and process all the updates gathered within the hour (or another time interval).
Polling triggers operate by regularly checking for new data or updates at set intervals, such as hourly. They initiate workflows based on this scheduled checking, processing all updates gathered during the interval. This ensures that changes are handled efficiently in bulk.
There is a default schedule set for a polling trigger once it's added to a workflow, but you can adjust the polling frequency in the trigger’s Configure submenu.
While the trigger step is open, click the Configure submenu, then select More Options. This will expand the additional setup options for the trigger where you can select the Schedule checkbox and reference the default frequency or change it.
In that view, you will be shown the next time that the trigger is scheduled to run after selecting a frequency, as long as the workflow is enabled.
You can change the polling frequency you'd like by navigating to the configure step of the trigger:
Every hour, or whatever frequency the polling is set at, MESA will look for any recent activity associated with the trigger and process all the updates gathered within the hour (or another time interval).
You will want to be sure you have successfully authenticated your trigger (if applicable). Please refer to our Credentials support guide to learn more!
All polling triggers will show the scheduled frequency underneath the title of the trigger in the builder.
For many triggers, especially those involving third-party apps, successful authentication is crucial. This process ensures MESA has the necessary permissions to access and interact with the apps used in your workflows. Please refer to our Credentials support guide for detailed instructions on authentication.
The Schedule trigger enables scheduling automated workflows either on a recurring basis or as a one-time event. For recurring schedules, workflows can be triggered at regular intervals, such as hourly or daily. Alternatively, the one-time option triggers a workflow at a specific date and time you select, occurring just once. This feature provides flexibility in automating tasks according to precise timing requirements.
Schedule triggers allow your workflow to run either on a recurring basis (hourly, daily, weekly) or as a one-time event at a specific date and time. This feature provides flexibility in automating tasks according to precise timing needs.
Webhooks are a popular standard on the internet for sending event notifications. MESA's Webhook trigger allows you to integrate any 3rd party service that supports them, even ones that don't have an integration yet.
Webhooks enable real-time data transfer from one application to another by sending HTTP requests to a specified URL. MESA’s Webhook Received trigger allows integration with any third-party service supporting webhooks, even if it lacks direct integration.
While webhooks are a great way to send "back end" event notifications, Web Requests allow a "front end" web client to send data to a workflow and receive a response.
Webhooks are excellent for backend event notifications, whereas Web Requests facilitate frontend data transfers, allowing a web client to send data to a workflow and receive responses.
The email trigger allows you to initiate an automation by sending an email to a unique MESA email address. The details within the email, including the subject, message body, and sender information, can be used as variables in subsequent steps of your workflow, enabling dynamic and responsive automation processes based on the content of the received email.
Email triggers start workflows when an email is sent to the unique MESA address located in the trigger. The email’s subject, body, and sender information become variables in the workflow, allowing you to tailor your automation based on the received content.
Automations can also be started every time a form is filled out. The form can be hosted on a MESA URL or embedded within your site. Like email, the contents of the form will be turned into variables that can be used within your workflow to customize the actions and drive the logic.
Form triggers initiate workflows when a form is submitted, either hosted on a MESA URL or embedded within your site. Similar to email triggers, the form responses are converted into variables used to customize the workflow actions.
The Google Forms trigger has the same process, but it will run based on a submission received from your linked Google Form.
