Automatically store Retell transcripts in Google Sheets/Airtable/Notion from webhook Overview This workflow stores the results of a Retell voice call (transcript, analysis, etc.) once it has ended and been analyzed. It listens for call_analyzed webhook events from Retell and stores the data in Airtable, Google Sheets, and Notion (choose based on your stack). Useful for anyone building Retell agents who want to keep a detailed history of analyzed calls in structured tools. Who is it for For builders of Retell's Voice Agents who want to store call history and essential analytic data. Prerequisites Have a Retell AI Account Create a Retell agent Associate a phone number with your Retell agent Set up one of the following: An Airtable base and table (example: "Transcripts") A Google Sheet with a “Transcripts” tab A Notion database with columns to match the transcript fields Templates: Airtable Google Sheets Notion How it works Receives a webhook POST request from Retell when a call has been analyzed.
Tags
Airtable
Google Sheets
NotionRelated workflows
See all Airtable→CWAuto-Post Medium.com Articles to LinkedIn with Telegram Alerts
🧠 Problem This Solves Manually sharing Medium articles to LinkedIn daily can be repetitive and time-consuming. This automation: Fetches the latest Medium articles based on a tag (e.g., android) Posts them on LinkedIn twice daily Uses Airtable to prevent duplicates Sends a confirmation to Telegram once posted Stay consistently active on LinkedIn without lifting a finger. 👥 Who This Template Is For Developers who write or follow Medium content Tech creators or founders looking to grow an audience Community or page managers needing regular curated posts Busy professionals who want hands-free LinkedIn engagement ⚙️ Workflow Breakdown This automation runs at 9:00 AM and 7:00 PM daily and performs these steps: Fetch articles from MediumAPI.com by tag Check Airtable to prevent reposting the same article Post on LinkedIn if it’s new Store the article ID in Airtable Send a Telegram message after successful posting 🧾 Step-by-Step Setup Instructions ✅ 1. Airtable Configuration Create a base with: Table Name: PostedArticles Column: ArticleID (Single line text – to track posted articles) 🔗 2. MediumAPI Setup Go to https://mediumapi.com Sign up and generate your API key from the dashboard Us
CTrack Amazon best seller ranks in Airtable with ScraperAPI and Slack
Quick overview This workflow runs daily at 8am to read an ASIN watchlist from Airtable, fetch each Amazon product’s Best Sellers Rank via ScraperAPI, store rank history back in Airtable, and post a consolidated Slack alert when a product’s rank change exceeds a configured threshold. How it works Runs every morning at 8am on a schedule. Searches Airtable for active watchlist items and processes them one at a time. Fetches each product’s Amazon data from ScraperAPI using the ASIN. Parses the Best Sellers Rank text into a numeric rank, calculates the change versus the previous saved rank, and flags items that exceed the watchlist threshold. Creates a new rank-history record in Airtable and updates the watchlist item with the latest rank and check time. Searches Airtable for today’s flagged rank-history records, builds a single digest message, and posts it to a Slack channel if any alerts exist. Setup Add Airtable credentials and select the Base/Table for both the watchlist search, the rank-history create step, the watchlist update step, and the “today’s alerts” search. Ensure your Airtable schema includes a Watchlist table with fields like active, asin, label, rank_threshold, last_ran
CW
Log Airtable worklogs to Tempo with Jira and Slack notifications
Quick overview This workflow runs nightly to pull time entries from Airtable, converts Jira issue keys to issue IDs, logs the time to Tempo via its REST API, archives the processed entries back to Airtable, and sends a confirmation message to a Slack user. How it works Runs on a schedule. Fetches all records from the Airtable “Daily Worklog” table. Looks up each entry’s Jira issue by Issue Key to retrieve the issue ID. Builds a Tempo worklog payload (authorAccountId, issueId, start date/time, description, and time spent calculated from start/end times). Sends each worklog to the Tempo to create the worklog entry. Archives each submitted entry into the Airtable “Worklog History” table and deletes the original record from “Daily Worklog”. Aggregates the processed records and sends a direct message in Slack confirming the upload. Setup Connect Airtable credentials and update the base ID and table IDs for “Daily Worklog” and “Worklog History” to match your Airtable setup. Connect Jira Software Cloud credentials with access to the projects/issues referenced by the Airtable Issue Key field. Connect an HTTP Bearer credential using your Tempo API token, and replace YOUR_TEMPO_AUTHOR_ID in