Setting Up a Trigger in Albato

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, just like Actions or the execution of formatting by Tools, sending 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 person responsible, 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: These 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: These 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 afterward, 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

Ensure your bundle is active: If the bundle is running, its status should display as "Pause" in the interface.

Check the trigger settings: Make sure all trigger parameters are correctly set. For instance, if the trigger depends on a specific event within an application, confirm that this event has indeed occurred.

Logs and records: Review the automation logs. It's possible that the trigger did activate, but the automation wasn't launched due to an error.

Inspect the Webhook or API: If the trigger is based on an API, there might be a delay of up to 5 minutes (depending on your subscription plan) between the bundle's activation and the trigger's event reception.

If it's a Webhook-type trigger, ensure that no additional setup was required for the chosen trigger. Most applications don't need this, but some might require you to copy a specific Albato URL into your application's settings. For such applications, Albato displays a special modal window during the trigger setup.




Filters: If the trigger has filters, ensure that the filtering conditions aren't preventing the trigger from activating.

If you're unable to determine the cause on your own, don't waste time. Reach out to our technical support specialists through the chat, and we'll be sure to assist you. It's free of charge!

Updated on: 26/09/2024