4 posts tagged with "workflows"

A common use case for Retool Workflows is to automate ETL tasks. Retool apps can query data from a variety of sources but it's much more efficient to prepare data outside of the frontend application.

This tutorial explains how to build an ETL workflow that:

• Extracts account data from Salesforce and transform it using JavaScript.
• Upserts the transformed data into a PostgreSQL database.
• Reads behavioral event data from a Google Sheet.
• Aggregates event data at an account level.
• Upserts aggregate event counts into a PostgreSQL database alongside account data.

The transformed data is then available to all Retool apps without the need for complex queries that run every time the app launches.

A common use case for Retool Workflows is to automatically alert on-call engineers and customer account managers if an incident occurs that is affecting customers, such as a service outage or downtime.

This tutorial explains how to build a notification workflow that:

• Runs automatically in response to a webhook event that occurs whenever an incident is logged in Intercom.
• Creates a ticket in Linear and assigns it to the on-call engineer for the affected product area.
• Notifies the customer's account manager on Slack.
• Evaluates the severity level to determine if the incident is urgent. If so, the workflow creates an incident in PagerDuty for escalation.

A common use case for Retool Workflows is to automatically compile metrics and generate reports by aggregating data from various sources.

This tutorial explains how to build a daily reporting workflow that:

• Retrieves opportunity, sales, and pipeline data from Salesforce.
• Retrieves monthly targets from a PostgreSQL database.
• Transforms and aggregates data using JavaScript.
• Sends HTML-formatted email reports using SMTP.
• Sends Slack notifications about any targets not currently met.

A common use case for Retool Workflows is to automate ETL (extract, transform, and load) tasks that transform and process data. Retool apps can directly interact with data from a variety of sources but it's much more efficient to automate ETL tasks than perform them in a frontend application.

This tutorial explains how to build a daily ETL and notification workflow that:

• Retrieves a list customers from a REST API.
• Filters results to exclude customers with personal email addresses and whose trial does not expire within 24 hours.
• Looks up data on company size using filtered email addresses with Clearbit.
• Sends a special offer email using SMTP to customers at companies with fewer than 50 employees.
• Notifies the Sales team in Slack of expiring trials for customers at companies with more than 50 employees.