Trigger Setup
IN THIS ARTICLE
A Trigger in Albato is an event within your chosen application that initiates your Automated Workflow. This could be a specific event, such as the addition of a new contact in HubSpot, or a periodic event like retrieving statistics from Google Ads.
Triggers are events in your app that start your automation (bundle) in Albato.
Triggers, just like Actions or the execution of formatting by Tools, send data about the event that occurred to Albato. For instance, a trigger for the appearance of a new task in your task manager would relay details like the task's title, description, status, the responsible person, and other fields filled out during the task's creation. The data fetched from the trigger can be integrated into Actions or formatting tools to be further relayed to other applications involved in the workflow.
Types of Triggers
Real-time Triggers are based on the Webhook technology. As soon as the selected event takes place in your application, it instantly sends a notification to Albato, setting your workflow in motion. When adding such a trigger, Albato provides a unique URL. To test the trigger, you can create a test event in your application to ensure everything operates correctly and to see the exact data sent with the event before the entire automated scenario is launched.
Scheduled Triggers operate based on API requests. Albato sends queries to your application at intervals ranging from 1 to 15 minutes to check for new events (during the trial period, the interval is 5 minutes, and afterwards, it depends on your subscription plan). If such events are detected, the workflow is initiated as many times as the number of events detected.
These triggers offer the flexibility of setting a schedule and frequency. For instance, you can set it to check for all new deals every Monday at 11:00 AM.
Trigger Filtering
You have the option to set filters for triggers to limit the initiation of the workflow. For example, you can configure the trigger so that the workflow only starts when a deal's status in HubSpot changes to Successfully Completed. This ensures your workflow is more targeted and efficient.
If your trigger isn't firing, follow these steps to troubleshoot the issue
Bundle status: Make sure your bundle is active. If it's running, you will see the Pause button.
Trigger settings: Verify that all trigger parameters are set correctly. If the trigger depends on a specific event, ensure that this event actually occurred in the source application.
Logs: Check the History tab. It's possible that the trigger worked, but the automation stopped because of an error.
Webhook or API:
For API-based triggers, there may be a delay of up to 5 minutes depending on the subscription plan.
For Webhook triggers, ensure that no additional configuration is required. Some apps require placing a specific Albato URL in their settings. Albato will show a modal window with this requirement during configuration if needed.
Filters: If your trigger includes filters, verify that the filtering conditions are not blocking event detection.
If you're unable to determine the cause on your own, you can always reach out to our technical support specialists through the live chat, and we'll gladly assist you.
Did this answer your question?