Triggers Overview
Triggers are post-execution actions that deliver your scraped data to external destinations. They run automatically after a project finishes successfully.
How Triggers Work
Section titled “How Triggers Work”- Your automation runs and extracts data.
- When the run completes, RTILA checks the project’s triggers.
- Each trigger is executed sequentially.
- Data flows from one trigger to the next via output variables.
Trigger Categories
Section titled “Trigger Categories”| Category | Triggers | Description |
|---|---|---|
| APIs/Webhooks | REST API, GraphQL, SOAP | Send data to any web API |
| Cloud Storage | AWS S3, GCP Storage, Azure Blob | Upload files to cloud storage |
| Databases | PostgreSQL, MySQL, MongoDB | Write data to databases |
| SMTP | Send email notifications | |
| File Formats | Export, Convert, Compress | Export and transform files |
| File Transfer | SFTP, FTPS, WebDAV | Transfer files to servers |
| Messaging Queues | RabbitMQ, Kafka, AWS SQS | Publish messages to queues |
| Spreadsheets | Google Sheets, Excel | Write data to spreadsheets |
| BI Tools & Alerting | Power BI, Tableau, Slack, Teams, Webhooks | Send alerts and BI data |
| ITSM, PM & ERP | JIRA, ServiceNow, SAP | Create tickets and records |
| Cloud Orchestration | Azure Data Factory, Dataiku, Airflow | Trigger pipeline runs |
| BI Tools | Qlik Sense, Superset, Looker, MicroStrategy | Interact with BI platforms |
| Cloud Warehouses | Snowflake, BigQuery, Databricks, MSSQL, Oracle | Query cloud data platforms |
| Data Stores & Search | Redis, Elasticsearch, Teradata, Sybase | Operate on data stores |
Configuring Triggers
Section titled “Configuring Triggers”- Go to Automation Projects.
- Select the project.
- Click Triggers in the ribbon.
- The Triggers Flow view opens.
- Click + to add a trigger.
- Choose a trigger type.
- Configure the trigger parameters.
Trigger Flow
Section titled “Trigger Flow”Triggers are connected in a flow:
Project Finish → Trigger 1 → Trigger 2 → Trigger 3 → ...Each trigger’s output can be used by the next trigger via output variables.
Output Variables
Section titled “Output Variables”Each trigger can save its output to a variable. The next trigger can reference it:
Trigger 1: REST API → output_variable: api_responseTrigger 2: Email → body: "API returned: ${api_response}"Bulk vs. Per-Record Triggers
Section titled “Bulk vs. Per-Record Triggers”| Type | Description | Examples |
|---|---|---|
| Bulk | Runs once with all data | Export to file, Parquet export, XML processing |
| Per-record | Runs for each record | REST API, Email, Database insert |
Bulk triggers are indicated with a “Bulk: runs once with all data” badge.
Deleting and Reordering Triggers
Section titled “Deleting and Reordering Triggers”- Click a trigger node to select it.
- Use the ← and → buttons to reorder.
- Click 🗑️ to delete.
- Click 📋 to clone.
