<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Thrum blog</title><link>https://www.thrum.run/blog</link><atom:link href="https://www.thrum.run/blog/rss.xml" rel="self" type="application/rss+xml"/><description>Posts and guides from Thrum, newest first.</description><language>en</language><lastBuildDate>Sat, 14 Nov 2026 12:00:00 GMT</lastBuildDate><item><title>How to add new Brevo list subscribers to Airtable</title><link>https://www.thrum.run/blog/brevo-list-contacts-to-airtable</link><guid isPermaLink="true">https://www.thrum.run/blog/brevo-list-contacts-to-airtable</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Copy each person who joins a Brevo list into a client's Airtable table within seconds, with the Thrum starter, Zapier, or Airtable's own webhook trigger.</description><content:encoded>&lt;p&gt;A client collects sign-ups in Brevo, through a form on their site or an imported spreadsheet, and runs the rest of the business from an Airtable base. Sooner or later they ask for every new subscriber to show up in that base too, so the team can follow up, tag them or count them. Thrum has a starter for exactly this, set off by Brevo the moment someone joins a chosen list. Other tools can do it as well, and the first two sections cover what their own pages say.&lt;/p&gt;
&lt;h2&gt;Zapier&lt;/h2&gt;
&lt;p&gt;Zapier&amp;#39;s Airtable and Brevo page lists templates in both directions. Two of them go from Brevo into Airtable, &amp;quot;Create new Airtable records every time new contacts are added to a specific list in Brevo&amp;quot; and &amp;quot;Add new Brevo contacts to Airtable as records instantly&amp;quot;. Its Brevo events include one that fires when a contact is added and one for contacts who unsubscribe from a campaign. Going the other way, templates such as &amp;quot;Add Brevo subscribers for new records in Airtable&amp;quot; push rows into Brevo.&lt;/p&gt;
&lt;h2&gt;Airtable&amp;#39;s &amp;quot;When webhook received&amp;quot; (data from outside)&lt;/h2&gt;
&lt;p&gt;Airtable can receive data from another service without any middle tool. Its &amp;quot;When webhook received&amp;quot; trigger (the event that starts an automation) gives you a unique address to paste into the other service&amp;#39;s webhook settings, and each request that arrives starts the automation, whose later steps can create a record. Airtable&amp;#39;s limits for it are 100 KB per request and five requests a second, and every request that starts a run counts toward the automation run limits of the workspace&amp;#39;s plan. Airtable also cautions that anyone who has the address can start the automation, so share it carefully.&lt;/p&gt;
&lt;p&gt;Whether Brevo can post its list events to an address like that, and in what shape, is a question for Brevo&amp;#39;s help centre. Brevo may also have its own way of sending contacts to Airtable, described there.&lt;/p&gt;
&lt;h2&gt;The Thrum way&lt;/h2&gt;
&lt;p&gt;The starter is called &amp;quot;Create a record in Airtable when a contact joins a list in Brevo&amp;quot;. When you switch it on, Thrum registers itself with the client&amp;#39;s Brevo using the client&amp;#39;s key, and Brevo then tells it about each join within seconds. Nothing has to be pasted into Brevo by hand.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Install from the library.&lt;/strong&gt; Go to Templates → Library, open the starter and install it into the client you are working for. It is switched off on arrival and comes with a checklist.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect Brevo.&lt;/strong&gt; In the client&amp;#39;s Brevo, open the account menu, then SMTP &amp;amp; API, then API Keys (Brevo&amp;#39;s name for its access keys), and generate a new key. Paste it in as the client&amp;#39;s Brevo connection (Thrum stores it encrypted in that client&amp;#39;s workspace).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect Airtable.&lt;/strong&gt; Make a token at airtable.com/create/tokens with data.records:read and data.records:write, and give it access to the client&amp;#39;s base.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fill in three fields.&lt;/strong&gt; &amp;quot;Brevo: List ID&amp;quot; is the number shown beside the list&amp;#39;s name under Contacts → Lists. &amp;quot;Airtable: Base ID&amp;quot; comes from the base&amp;#39;s address, the part that starts with app. &amp;quot;Airtable: Table&amp;quot; is the name of the table that receives the rows.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Match the column names.&lt;/strong&gt; Each join writes one row with three values. &amp;quot;Their email&amp;quot; holds the subscriber&amp;#39;s address, &amp;quot;Lists it joined&amp;quot; holds the list&amp;#39;s ID, and &amp;quot;When&amp;quot; holds the time Brevo gives for the event. Airtable only accepts names that match the table&amp;#39;s columns exactly, so either add columns with those names or rename the three in the step to the client&amp;#39;s own, such as Email, List and Joined.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Switch it on and test.&lt;/strong&gt; Add yourself to the list through the client&amp;#39;s signup form. The row appears in Airtable within seconds.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;Things that behave in a particular way&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Each join is one row, once.&lt;/strong&gt; Brevo sends no unique number with these events, so Thrum treats the event type, the email and the time together as the event&amp;#39;s identity. If Brevo delivers the same event twice, the second copy starts nothing.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Creating a row is not repeated blindly.&lt;/strong&gt; When Airtable is busy or has a server error, the step is tried again after 5 seconds and then at doubling waits, up to 3 attempts. If the connection drops after the request reached Airtable, the row may already exist, so Thrum stops and says so, and you retry the run once you have looked.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Turning it off unregisters it.&lt;/strong&gt; Switching the workflow off, or changing its starting event or the Brevo key, removes the old registration from the client&amp;#39;s Brevo, so a paused workflow leaves nothing listening.&lt;/p&gt;
&lt;h2&gt;Related ways to join the two&lt;/h2&gt;
&lt;p&gt;Brevo has two more starters that write to Airtable. &amp;quot;A contact&amp;#39;s details change&amp;quot; also arrives within seconds, and &amp;quot;A new contact is added&amp;quot; is checked every 15 minutes and records the contact&amp;#39;s email, when it was created and whether it is unsubscribed from email. Starting from Airtable instead, new or edited rows can set off a plain-text Brevo email, sent from an address the client has verified with Brevo. The &lt;a href=&quot;https://www.thrum.run/integrations/airtable/brevo&quot;&gt;Airtable and Brevo page&lt;/a&gt; lists each of them with its starter.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/airtable/integrations/brevo&quot;&gt;https://zapier.com/apps/airtable/integrations/brevo&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/docs/when-webhook-received-trigger&quot;&gt;https://support.airtable.com/docs/when-webhook-received-trigger&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to post in Discord when an Airtable record is added</title><link>https://www.thrum.run/blog/discord-message-new-airtable-record</link><guid isPermaLink="true">https://www.thrum.run/blog/discord-message-new-airtable-record</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Post a notice in a Discord channel each time a client's Airtable table gets a new row, with a script, with Zapier, or with a Thrum starter set up in six steps.</description><content:encoded>&lt;p&gt;Plenty of small organisations, such as a cleaning crew, a club or a paid community, run their people in a Discord server. When their sign-ups, jobs or orders sit in Airtable, it helps to drop a short post into a channel whenever a new row appears. Thrum does this with a starter that uses a Discord webhook (a posting address made in the client&amp;#39;s server), and there are two other routes worth knowing first.&lt;/p&gt;
&lt;h2&gt;Route one: a script inside Airtable&lt;/h2&gt;
&lt;p&gt;Airtable&amp;#39;s automations have no general action for sending a request to another service, and its help centre says so directly. For outbound calls it points to the &amp;quot;Run a script&amp;quot; action, where a script calls fetch() and can then pass results to later steps. A sensitive value, such as the secret part of an address, goes in the script editor&amp;#39;s Secrets, which other editors can run but not read. Each run allows up to 50 fetch requests, and a fetch times out after 30 seconds.&lt;/p&gt;
&lt;p&gt;So a script can post to Discord, provided someone writes and maintains it. Discord may document its own ways to receive posts from other tools, and Discord&amp;#39;s help centre is the place to check what it offers.&lt;/p&gt;
&lt;h2&gt;Route two: Zapier&lt;/h2&gt;
&lt;p&gt;Zapier&amp;#39;s Airtable and Discord page has templates such as &amp;quot;Send Discord channel messages for new Airtable records in views&amp;quot;, and Discord events like &amp;quot;New Message Posted to Channel&amp;quot; for the opposite direction. Its Airtable &amp;quot;New Record&amp;quot; event starts for newly created records, or for records the first time they show up in a chosen view, and on the Free plan Zapier checks for new data every 15 minutes.&lt;/p&gt;
&lt;h2&gt;Route three: the Thrum starter&lt;/h2&gt;
&lt;p&gt;The starter is &amp;quot;Post a message in Discord when a record is added in Airtable&amp;quot;. The Discord side of it needs no channel picker. A Discord webhook (that posting address) belongs to exactly one channel, so the address you paste in decides where every post lands.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Install it into the client.&lt;/strong&gt; In Templates → Library, open the starter, choose the client and install. It arrives switched off with a checklist of two accounts and two fields.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Create the Discord webhook.&lt;/strong&gt; In the client&amp;#39;s server, open Server Settings, then Integrations (Discord&amp;#39;s name for the menu), then Webhooks, make a new one, pick the channel and copy its address. Paste it in as the client&amp;#39;s Discord connection. Anyone holding that address can post to the channel, so Thrum stores it encrypted with the client&amp;#39;s other keys.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Create the Airtable token.&lt;/strong&gt; At airtable.com/create/tokens, add the scopes data.records:read and data.records:write and grant it the client&amp;#39;s base.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fill in the base and table.&lt;/strong&gt; &amp;quot;Airtable: Base ID&amp;quot; is the appXXXXXXXXXXXXXX code from the base&amp;#39;s address, and &amp;quot;Airtable: Table&amp;quot; is the name of the table to watch, such as Leads. Those are the only two fields.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Shape the post.&lt;/strong&gt; Out of the box, each post reads &amp;quot;A record is added in Airtable.&amp;quot; with an &amp;quot;Added at:&amp;quot; line holding the row&amp;#39;s creation time. Edit the Discord step to pull in the row&amp;#39;s own columns (a Job column, for instance, is &lt;code&gt;{{ trigger.payload.fields.Job }}&lt;/code&gt;). Discord takes at most 2,000 characters per message, so keep long text fields out or shorten them first.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Switch it on.&lt;/strong&gt; Every 15 minutes Thrum asks Airtable for rows added since the last check and posts one message for each, oldest first. Anything that was in the table beforehand does not post.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;Posting when a row changes&lt;/h2&gt;
&lt;p&gt;Some clients care less about new rows than about rows reaching a stage, a shift confirmed or a job marked done. For that, use the second starter, &amp;quot;Post a message in Discord when a record is changed in Airtable&amp;quot;. Airtable only says a row changed through a field, so the table needs a field of the type &amp;quot;Last modified time&amp;quot;, limited to the columns that matter, and you name it in the starter. You can also restrict it to one view, which turns it into &amp;quot;a record enters this view&amp;quot;. It checks every 15 minutes like the first.&lt;/p&gt;
&lt;h2&gt;Editing a post instead of adding another&lt;/h2&gt;
&lt;p&gt;The Discord step list includes &amp;quot;Edit a message&amp;quot;, which changes a post made earlier through the same address. That keeps a channel tidy when one row moves through stages, since the original notice updates in place. A message posted by anyone else, or through a different address, can&amp;#39;t be edited this way.&lt;/p&gt;
&lt;h2&gt;If Discord is unreachable&lt;/h2&gt;
&lt;p&gt;When Discord answers with a server error or asks Thrum to slow down, the step waits and tries again, from 5 seconds upward, up to 3 attempts. When the connection breaks after the post was sent, Thrum stops and marks the run as possibly delivered, leaving the retry to you, so members never see the same notice twice by accident. An address that has been deleted in Discord makes the step fail, which shows on the client&amp;#39;s health.&lt;/p&gt;
&lt;p&gt;Every pairing of the two apps, with each starter, is on the &lt;a href=&quot;https://www.thrum.run/integrations/airtable/discord&quot;&gt;Airtable and Discord page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/docs/run-a-script-action&quot;&gt;https://support.airtable.com/docs/run-a-script-action&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/airtable/integrations/discord&quot;&gt;https://zapier.com/apps/airtable/integrations/discord&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to create a Freshdesk ticket for a new Shopify order</title><link>https://www.thrum.run/blog/freshdesk-ticket-new-shopify-order</link><guid isPermaLink="true">https://www.thrum.run/blog/freshdesk-ticket-new-shopify-order</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Open a Freshdesk ticket for every new Shopify order, with its number, email and total, using Zapier or a Thrum starter, and where Freshdesk's Shopify app fits.</description><content:encoded>&lt;p&gt;Some shops want a support ticket waiting for each order. A made-to-order business might check each one by hand, a shop with tricky delivery might track each parcel as a ticket, and a support team might prefer to have the order on file before the customer writes in. This guide covers how to open that ticket automatically. Thrum does it with a starter on the client&amp;#39;s own Shopify store and Freshdesk helpdesk. Freshdesk&amp;#39;s own Shopify app and Zapier are described first, from their own pages.&lt;/p&gt;
&lt;h2&gt;Freshdesk&amp;#39;s Shopify app&lt;/h2&gt;
&lt;p&gt;Freshdesk&amp;#39;s help centre describes a Shopify app that brings a customer&amp;#39;s order information into the helpdesk. Once installed, a Shopify panel appears on the ticket details page, and on each contact&amp;#39;s page, showing the customer&amp;#39;s current and past orders with payment and shipping details. Agents can use Shopify placeholders in canned responses, and with the right settings they can issue refunds and cancel orders from the panel. Connecting a store means creating a custom app in Shopify, and Freshdesk&amp;#39;s article notes that from 1 January 2026 new custom apps are created and managed in the Shopify Dev Dashboard.&lt;/p&gt;
&lt;p&gt;That app puts order details beside tickets that already exist. It is the right tool when tickets start from customers&amp;#39; emails. When the goal is a new ticket for each order, it needs something else to create the ticket.&lt;/p&gt;
&lt;h2&gt;Zapier&lt;/h2&gt;
&lt;p&gt;Zapier&amp;#39;s Freshdesk and Shopify page lists a Freshdesk action that creates a ticket &amp;quot;for your domain&amp;quot;, and Shopify events that fire when an order is created or when an order is paid, among many others. Its Freshdesk side also has events for new tickets and notes, and an action to update a ticket.&lt;/p&gt;
&lt;h2&gt;The Thrum starter&lt;/h2&gt;
&lt;p&gt;The starter is &amp;quot;Open a ticket in Freshdesk when a new order comes in in Shopify&amp;quot;. It has nothing to fill in apart from the two connections.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Install into the client.&lt;/strong&gt; Templates → Library, open the starter, choose the client and install. It is switched off until the two accounts are connected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect Shopify.&lt;/strong&gt; This works for a store that already has a custom app made by its admin. In the Shopify admin, go to Apps → Develop apps, open that app and check its Admin API scopes (the permissions it holds) include read_orders and write_customers. Copy the token from the app&amp;#39;s settings. Shopify shows it once when it is created, so if it is gone, generate a new one.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect Freshdesk.&lt;/strong&gt; Thrum asks for two values. The helpdesk subdomain is the first part of the client&amp;#39;s Freshdesk address, so northside for northside.freshdesk.com. The key is under the agent&amp;#39;s profile picture, then Profile settings, then View API key (the agent&amp;#39;s personal access key).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Look at the ticket it opens.&lt;/strong&gt; Every order becomes a new ticket, open and at low priority. Its subject starts &amp;quot;A new order comes in:&amp;quot; and ends with the shop&amp;#39;s order number, such as #1001, and the order&amp;#39;s email address is set as the requester. The body repeats the order number and email and adds the total, its currency and whether it is paid. Two edits are worth making once it is installed. Put the customer&amp;#39;s first and last name, which the order step provides, into the requester name. If delivery questions come through these tickets, add the fulfilment status to the body as well.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Switch it on.&lt;/strong&gt; Thrum checks the store every 5 minutes and opens one ticket for each order placed since the previous check, oldest first. Orders placed before the workflow went live are skipped.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;Tickets for paid orders&lt;/h2&gt;
&lt;p&gt;If the team should only see orders whose payment went through, install &amp;quot;Open a ticket in Freshdesk when an order is paid in Shopify&amp;quot; in its place. It checks every 5 minutes, opens one ticket per order however often the order changes afterwards, and its subject begins &amp;quot;An order is paid:&amp;quot;.&lt;/p&gt;
&lt;h2&gt;No duplicate tickets&lt;/h2&gt;
&lt;p&gt;Thrum takes care that one order opens one ticket. Each order has an identity, so overlapping checks start nothing new. A busy or failing Freshdesk is retried at waits that begin at 5 seconds and double, up to 3 attempts. If the connection breaks after Freshdesk received the request, Thrum does not send it again on its own, since the ticket may already exist, and the run tells you to check before retrying.&lt;/p&gt;
&lt;h2&gt;Closing the loop&lt;/h2&gt;
&lt;p&gt;Freshdesk has a second step in Thrum, &amp;quot;Update a ticket&amp;quot;, which moves a ticket to a status such as Pending or Resolved, and can change its priority or agent, found by the ticket&amp;#39;s id. Freshdesk can also start workflows, when a ticket is opened and when one is resolved or closed, with Thrum looking for both every 5 minutes. A workflow started that way can reach back into Shopify with &amp;quot;Create a customer&amp;quot; or &amp;quot;Update a customer&amp;quot;. The &lt;a href=&quot;https://www.thrum.run/integrations/freshdesk/shopify&quot;&gt;Freshdesk and Shopify page&lt;/a&gt; lists all the combinations.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://support.freshdesk.com/support/articles/195382-shopify-integration-to-bring-in-customer-order&quot;&gt;https://support.freshdesk.com/support/articles/195382-shopify-integration-to-bring-in-customer-order&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/freshdesk/integrations/shopify&quot;&gt;https://zapier.com/apps/freshdesk/integrations/shopify&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to log Postmark bounces in Airtable</title><link>https://www.thrum.run/blog/postmark-bounces-to-airtable</link><guid isPermaLink="true">https://www.thrum.run/blog/postmark-bounces-to-airtable</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Record every bounced Postmark email as a row in a client's Airtable base within seconds, with the reason and whether the address is deactivated, using Thrum.</description><content:encoded>&lt;p&gt;When a receipt bounces, the customer never sees it. If a client sends transactional email through Postmark and keeps customers in Airtable, a bounce log in the base lets the team fix the address, phone the customer or stop sending to a dead inbox. Thrum&amp;#39;s starter writes a row for each bounce within seconds of Postmark reporting it. This guide also covers Zapier and Airtable&amp;#39;s own way of receiving data, both as their pages describe them.&lt;/p&gt;
&lt;h2&gt;Zapier&lt;/h2&gt;
&lt;p&gt;Zapier&amp;#39;s Airtable and Postmark page (where Postmark is listed as ActiveCampaign Postmark) describes its Postmark bounce event with the line &amp;quot;If an email sent from Postmark bounces because of a delivery issue, you may be notified of that bounce right away by setting up a Bounce Webhook.&amp;quot; Zapier marks it as starting a Zap instantly, and its Airtable actions include creating a record. The ready-made templates on that page run the other way, sending Postmark emails for new or updated Airtable records.&lt;/p&gt;
&lt;h2&gt;Receiving the events in Airtable itself&lt;/h2&gt;
&lt;p&gt;Airtable can take in events from another service through its &amp;quot;When webhook received&amp;quot; automation trigger (the starting event for data sent from outside). It gives you a unique address to paste into that service&amp;#39;s settings, and later steps in the automation can create a record from what arrives. Airtable&amp;#39;s limits are 100 KB per request and five requests a second, and each request that starts a run counts toward the run limits of the workspace&amp;#39;s plan. Anyone with the address can start the automation, so Airtable asks you to think about where it is shared. How Postmark&amp;#39;s bounce events would be pointed at such an address, and what they contain, is covered in Postmark&amp;#39;s help centre, which also describes any options Postmark has of its own.&lt;/p&gt;
&lt;h2&gt;The Thrum starter&lt;/h2&gt;
&lt;p&gt;&amp;quot;Create a record in Airtable when an email bounces in Postmark&amp;quot; registers itself with the client&amp;#39;s Postmark server when you switch it on, using the client&amp;#39;s server token. Postmark then tells Thrum about each bounce as it happens. Switching the workflow off removes that registration again.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Install the starter.&lt;/strong&gt; Find it under Templates → Library and install it into the client whose Postmark server sends the emails. It arrives switched off with a short checklist.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect Postmark.&lt;/strong&gt; In Postmark, open the client&amp;#39;s server, then API Tokens, and copy the Server API token (the key Thrum sends with). The token belongs to one server, so pick the server that sends the client&amp;#39;s mail.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect Airtable.&lt;/strong&gt; Create a token at airtable.com/create/tokens with data.records:read and data.records:write, and grant it the client&amp;#39;s base.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fill in three fields.&lt;/strong&gt; &amp;quot;Postmark: Message stream&amp;quot; names the Postmark stream that carries these emails, which is &amp;quot;outbound&amp;quot; on a server with no others. &amp;quot;Airtable: Base ID&amp;quot; is the part of the base&amp;#39;s address that begins with app, and &amp;quot;Airtable: Table&amp;quot; names the table that holds the log, such as Bounces.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Line up the columns.&lt;/strong&gt; Every bounce writes four values. &amp;quot;Address that bounced&amp;quot; is the recipient&amp;#39;s address. &amp;quot;Bounce type HardBounce&amp;quot; carries Postmark&amp;#39;s name for the type of bounce, HardBounce being one of them. &amp;quot;What happened&amp;quot; carries Postmark&amp;#39;s description of the failure, and &amp;quot;Address now deactivated&amp;quot; is true when the bounce led Postmark to deactivate the address. Airtable only accepts names that match the table&amp;#39;s columns, so create those four columns or rename the values to the client&amp;#39;s own.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Switch it on.&lt;/strong&gt; From here, a bounce on that stream lands in the table within seconds.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;Why one bounce makes one row&lt;/h2&gt;
&lt;p&gt;Each event Thrum receives has an identity, and if the same event arrives a second time, the copy starts nothing, so the log never doubles up. Creating the row is handled carefully too. If Airtable is busy or fails, the step is retried at waits that start at 5 seconds and double, up to 3 attempts, but if the connection breaks after the request reached Airtable, Thrum marks the run as possibly done and leaves the retry to you.&lt;/p&gt;
&lt;h2&gt;The other Postmark starters&lt;/h2&gt;
&lt;p&gt;Clicks can be logged the same way. &amp;quot;Create a record in Airtable when a link in an email is clicked in Postmark&amp;quot; records who clicked, the link, the device and whether the link was in the HTML or the text part. Clicks need tracked links on the emails, and opens are a different matter, because Thrum&amp;#39;s own email step sends plain text, which Postmark cannot track for opens. In the other direction, an Airtable row that is new or edited can start a plain-text email from the client&amp;#39;s Postmark server, or fill one of the client&amp;#39;s Postmark templates with values from the run, such as a booking confirmation. Each From address has to be a confirmed sender signature or sit on a verified domain.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;https://www.thrum.run/integrations/airtable/postmark&quot;&gt;Airtable and Postmark page&lt;/a&gt; lists every combination of the two with its starter.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/airtable/integrations/postmark&quot;&gt;https://zapier.com/apps/airtable/integrations/postmark&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/docs/when-webhook-received-trigger&quot;&gt;https://support.airtable.com/docs/when-webhook-received-trigger&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to save Telegram messages to Notion</title><link>https://www.thrum.run/blog/save-telegram-messages-to-notion</link><guid isPermaLink="true">https://www.thrum.run/blog/save-telegram-messages-to-notion</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Turn each message sent to a client's Telegram bot into a row in a Notion database within seconds, with Zapier or a Thrum starter, and what to change after.</description><content:encoded>&lt;p&gt;Thrum has a starter that saves every message sent to a client&amp;#39;s Telegram bot as a row in their Notion database, and Zapier offers a template for the same job. Field staff, drivers and clients themselves often find a quick Telegram message the easiest way to send a request, a reading from a site visit or a note that a job is done. The trouble starts when those messages need finding again next week, and a database row gives the team something to sort, assign and tick off.&lt;/p&gt;
&lt;h2&gt;Zapier&lt;/h2&gt;
&lt;p&gt;Zapier&amp;#39;s Notion and Telegram page includes the template &amp;quot;Create new items in Notion from new Telegram messages&amp;quot;. On the Telegram side, Zapier&amp;#39;s event starts instantly when your bot receives a message, and the Notion side lists actions such as updating a data source item, or finding one and creating it when it does not exist (data source is the term Zapier uses). Most of the other templates on that page go the opposite way, sending Telegram messages when Notion items are added or updated.&lt;/p&gt;
&lt;p&gt;Notion and Telegram may each offer ways of their own to connect the two, and Notion&amp;#39;s help centre and Telegram&amp;#39;s bot documentation are where to look for them.&lt;/p&gt;
&lt;h2&gt;Setting it up in Thrum&lt;/h2&gt;
&lt;p&gt;The starter is &amp;quot;Add a database row in Notion when a message is sent to the bot in Telegram&amp;quot;. Telegram tells Thrum about each message within seconds of it reaching the bot.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Install the starter.&lt;/strong&gt; In Templates → Library, open it and install it into the client. It starts switched off, with a checklist of two connections and two fields.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Create the bot.&lt;/strong&gt; In Telegram, message @BotFather, send /newbot and copy the token. Paste it as the client&amp;#39;s Telegram connection. Then add the bot to the client&amp;#39;s group, or have the client message it once.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Create the Notion connection.&lt;/strong&gt; At notion.so/profile/integrations, make a new internal integration (Notion&amp;#39;s word for a connection) in the client&amp;#39;s workspace. Tick the capabilities Read content, Insert content and Update content, and copy the secret. Then open the database, choose ••• then Connections, and add it there (this is what lets it reach that database). The starter needs that last step to reach the database.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fill in the two fields.&lt;/strong&gt; &amp;quot;Notion: Database ID&amp;quot; is the 32 characters in the database&amp;#39;s address. &amp;quot;Notion: Title column&amp;quot; is the name of the database&amp;#39;s title property, often Name.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Change the title to the message.&lt;/strong&gt; As installed, each row&amp;#39;s title is the chat&amp;#39;s group name, which is the same for every message from one group. Open the Notion step and set the title to the message itself (&lt;code&gt;{{ trigger.payload.text }}&lt;/code&gt;). The trigger (the step that starts the workflow) also carries the sender&amp;#39;s first and last name, their username, the chat&amp;#39;s ID and type, and when the message was sent, so you can work any of them into the title.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Set defaults in Notion, then switch on.&lt;/strong&gt; The step sets the title only. Notion types its other columns itself, so give a Status or an Assignee column a default in Notion, and new rows arrive ready to sort. Switch the workflow on and send the bot a test message. A row appears in the database within seconds.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;Two Telegram rules to plan around&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;One bot, one listener.&lt;/strong&gt; A Telegram bot sends its incoming messages to one place. Thrum lets one workflow listen per bot, and no other tool can read that bot&amp;#39;s messages at the same time. If the client already uses a bot elsewhere, make a new one for this.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Groups hear less by default.&lt;/strong&gt; In a group, the bot only sees commands, replies to it and messages that mention it. To save every message in the group, turn privacy mode off for the bot in BotFather.&lt;/p&gt;
&lt;h2&gt;When Notion is slow or refuses&lt;/h2&gt;
&lt;p&gt;If Notion is busy or answers with a server error, Thrum tries the step again after 5 seconds and then at doubling waits, up to 3 attempts. Any other refusal fails the step at once, and the first thing to check is the connection from step 3 (the database&amp;#39;s Connections list). Adding a row is never repeated after a dropped connection without you, because the row may already be there.&lt;/p&gt;
&lt;h2&gt;Going the other way&lt;/h2&gt;
&lt;p&gt;The same pair can post into Telegram when the database changes. &amp;quot;Send a message in Telegram when a row is added to a database in Notion&amp;quot; checks every 15 minutes and sends the page&amp;#39;s link, when it was added and when it was last edited, to the chat ID you give. The version for changed rows works the same way. Notion rounds edit times to the minute, so two edits within one minute count as one change. Both use the data source ID from the database&amp;#39;s settings, under Manage data sources. The &lt;a href=&quot;https://www.thrum.run/integrations/notion/telegram&quot;&gt;Notion and Telegram page&lt;/a&gt; lists all of these with their starters.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/notion/integrations/telegram&quot;&gt;https://zapier.com/apps/notion/integrations/telegram&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/airtable/integrations/telegram&quot;&gt;https://zapier.com/apps/airtable/integrations/telegram&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to send a SendGrid email when an Airtable record is created</title><link>https://www.thrum.run/blog/sendgrid-email-new-airtable-record</link><guid isPermaLink="true">https://www.thrum.run/blog/sendgrid-email-new-airtable-record</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Three ways to email someone through SendGrid when a row is added to Airtable, compared, then the Thrum starter set up step by step on a client's own accounts.</description><content:encoded>&lt;p&gt;A booking request, an order or a job card lands in a client&amp;#39;s Airtable base, and somebody needs an email about it. You can do that with Airtable&amp;#39;s own email action, with a general automation tool such as Zapier, or with a Thrum starter that sends through the client&amp;#39;s own SendGrid account. Below is what each route does according to its documentation, followed by the Thrum setup from start to finish.&lt;/p&gt;
&lt;h2&gt;Airtable&amp;#39;s built-in Send email action&lt;/h2&gt;
&lt;p&gt;Airtable automations include a &amp;quot;Send an email&amp;quot; action. You start with the &amp;quot;When record created&amp;quot; trigger (the event that starts the automation), add the action, then fill in recipients, a subject and a body. The plus button inserts values from the new record, and &amp;quot;Show more options&amp;quot; adds CC, BCC, a From name and a reply-to address.&lt;/p&gt;
&lt;p&gt;The recipient rules are the part to read before using it for client work. Airtable lets the action email verified collaborators on the base without a daily cap. For anyone else, the allowance depends on the plan. On Free, each recipient has to be a verified collaborator. Team can reach 100 unique outside addresses a day and Business 1,000, and all plans have a ceiling of 1,000 recipients per run.&lt;/p&gt;
&lt;p&gt;Airtable also warns about two habits of that starting event. Switching an automation on does nothing for rows already in the table, and a record typed in by hand will likely set it off before the person has finished typing. For hand-entered rows, Airtable suggests &amp;quot;When record matches conditions&amp;quot; or &amp;quot;When record enters view&amp;quot; instead.&lt;/p&gt;
&lt;p&gt;This action sends the mail from Airtable itself. For an email that leaves from the client&amp;#39;s verified SendGrid sender, Airtable&amp;#39;s help centre points to the &amp;quot;Run a script&amp;quot; action, which can call outside services with fetch(). Keys belong in the script editor&amp;#39;s Secrets, a run can make up to 50 fetch requests, and each fetch times out after 30 seconds. SendGrid may offer another route as well, and SendGrid&amp;#39;s help centre is the place to look for it.&lt;/p&gt;
&lt;h2&gt;Zapier&lt;/h2&gt;
&lt;p&gt;Zapier lists a ready-made template called &amp;quot;Send email from SendGrid for new Airtable records&amp;quot;, built from Airtable&amp;#39;s &amp;quot;New Record&amp;quot; and SendGrid&amp;#39;s &amp;quot;Send Email&amp;quot;. Zapier says this fires for a newly created record, or for new or existing records when they first enter a view you choose. On Zapier&amp;#39;s Free plan it checks for new data every 15 minutes.&lt;/p&gt;
&lt;h2&gt;Setting it up in Thrum&lt;/h2&gt;
&lt;p&gt;In Thrum each client is a separate workspace holding that client&amp;#39;s keys, so this starter sends from the client&amp;#39;s SendGrid and reads the client&amp;#39;s Airtable, and you repeat it per client from the same template.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Install the starter.&lt;/strong&gt; Open Templates → Library, find &amp;quot;Send an email in SendGrid when a record is added in Airtable&amp;quot; and choose the client it is for. It installs switched off, with a checklist of the accounts to connect and the fields to fill in.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect Airtable.&lt;/strong&gt; At airtable.com/create/tokens, create a token with the scopes data.records:read and data.records:write, add the client&amp;#39;s base to it, and paste it into the checklist.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect SendGrid.&lt;/strong&gt; In the client&amp;#39;s SendGrid, go to Settings → API Keys and create a key with Mail Send access (the key is the password Thrum sends with). The From address must be a verified sender there, or SendGrid refuses the email.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fill in four fields.&lt;/strong&gt; &amp;quot;SendGrid: From address&amp;quot; takes the sender, for example &lt;a href=&quot;mailto:hello@northside.example&quot;&gt;hello@northside.example&lt;/a&gt;. &amp;quot;Who it goes to (SendGrid)&amp;quot; is the address that gets the email, yours or the client&amp;#39;s team. &amp;quot;Airtable: Base ID&amp;quot; is the appXXXXXXXXXXXXXX code, and &amp;quot;Airtable: Table&amp;quot; is the table&amp;#39;s name, such as Leads.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Make the email say something useful.&lt;/strong&gt; As installed, the subject is &amp;quot;A record is added&amp;quot; and the plain-text body has two lines, &amp;quot;A record is added in Airtable.&amp;quot; and &amp;quot;Added at:&amp;quot; with the creation time Airtable gives the row. Open the email step and add the columns your reader needs. Every column of the new row is available by name (a Name column is &lt;code&gt;{{ trigger.payload.fields.Name }}&lt;/code&gt;) in the subject and the body.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Switch it on.&lt;/strong&gt; From then on, Thrum checks the table every 15 minutes and sends one email for each row added since the last check, oldest first. Rows that were already in the table are left out.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;When a send fails&lt;/h2&gt;
&lt;p&gt;A busy answer from SendGrid (status 429) or a server error is tried again, 5 seconds later and then at doubling waits, up to 3 attempts by default. A send whose connection broke after the request left is handled differently. Thrum does not repeat it by itself, since the email may already be in someone&amp;#39;s inbox, and the run says it may have gone through so you can check and retry it by hand. If the client&amp;#39;s Airtable token stops working, the failed checks raise an alert that names the app.&lt;/p&gt;
&lt;h2&gt;Which one to pick&lt;/h2&gt;
&lt;p&gt;Airtable&amp;#39;s email action is enough when the people being emailed are collaborators or fit inside the plan&amp;#39;s daily allowance, and the sender address doesn&amp;#39;t matter. Zapier connects the two through a Zapier account and plans, as its template page describes. Thrum suits an agency or freelancer running this for several clients, each with mail from their own SendGrid sender and checklist. The &lt;a href=&quot;https://www.thrum.run/integrations/airtable/sendgrid&quot;&gt;Airtable and SendGrid page&lt;/a&gt; lists the other combinations, including logging SendGrid bounces and link clicks back into Airtable.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/articles/1091012569-airtable-automation-action-send-email&quot;&gt;https://support.airtable.com/articles/1091012569-airtable-automation-action-send-email&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/articles/5081141887-airtable-automation-trigger-when-record-created&quot;&gt;https://support.airtable.com/articles/5081141887-airtable-automation-trigger-when-record-created&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/docs/run-a-script-action&quot;&gt;https://support.airtable.com/docs/run-a-script-action&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/airtable/integrations/sendgrid&quot;&gt;https://zapier.com/apps/airtable/integrations/sendgrid&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to send a Slack message when an Airtable record is created</title><link>https://www.thrum.run/blog/slack-message-new-airtable-record</link><guid isPermaLink="true">https://www.thrum.run/blog/slack-message-new-airtable-record</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Airtable's own Slack options, Zapier and a Thrum starter compared for posting in a client's Slack channel whenever their Airtable base gets a new record.</description><content:encoded>&lt;p&gt;Your client&amp;#39;s team lives in Slack and their work lives in Airtable, and they want a post in #leads each time the base gains a row. Airtable can do some of this by itself, Zapier can do it through its templates, and Thrum has a starter that posts with the client&amp;#39;s own Slack app. This guide walks through all of them and ends with the Thrum setup in full.&lt;/p&gt;
&lt;h2&gt;Inside Airtable, two options&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Base activity notifications.&lt;/strong&gt; Airtable has a Slack feature that is separate from automations. From the menu beside a base&amp;#39;s name you choose Slack notifications, then pick the base and the channel the updates go to. You can add as many of these rules as you need, so one base can post to #recruiting and another to #dev. Airtable lists its limits plainly. A record that enters a view because of a time-based filter sends no notification, and in a view, changes to hidden fields are ignored.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The &amp;quot;Slack: Send a message&amp;quot; action.&lt;/strong&gt; In an automation, you add Slack from the actions menu (it sits under Integrations) and connect a Slack account. A fixed recipient is a single channel or user. The message can be fixed text, values from the record, or a mix, with Markdown for formatting, @mentions and a link back to the record. Posts show as coming from Airtable with its logo unless you change the bot&amp;#39;s name and picture. Airtable asks for one successful test before the automation can be turned on, and a test with &amp;quot;Run as configured&amp;quot; posts for real (warn the channel first). There is also &amp;quot;Slack: Send an actionable message&amp;quot;, which adds buttons that update the record and expires after 7 days without activity.&lt;/p&gt;
&lt;p&gt;One detail from Airtable&amp;#39;s notes about the &amp;quot;When record created&amp;quot; event applies to both. A row typed in by hand will likely set the automation off before the person has finished, so Airtable recommends &amp;quot;When record matches conditions&amp;quot; or &amp;quot;When record enters view&amp;quot; for rows people enter themselves.&lt;/p&gt;
&lt;h2&gt;Zapier&lt;/h2&gt;
&lt;p&gt;Zapier&amp;#39;s Airtable and Slack page offers templates such as &amp;quot;Post new Airtable records to Slack&amp;quot; and &amp;quot;Post notifications about new Airtable records in a view to Slack&amp;quot;. Its Airtable &amp;quot;New Record&amp;quot; event covers new records, and existing ones the first time they enter a chosen view. Zapier checks for new data every 15 minutes on its Free plan.&lt;/p&gt;
&lt;h2&gt;The Thrum starter, step by step&lt;/h2&gt;
&lt;p&gt;Thrum keeps each client in a separate workspace with their own keys, stored encrypted, so the post comes from an app in the client&amp;#39;s Slack and the base is read with the client&amp;#39;s Airtable token.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Pick it from the library.&lt;/strong&gt; Under Templates → Library, open &amp;quot;Post a message in Slack when a record is added in Airtable&amp;quot; and install it into the client. It lands switched off, with a checklist.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Make the client&amp;#39;s Slack app.&lt;/strong&gt; In the client&amp;#39;s Slack, go to api.slack.com/apps (the page where Slack apps are made), create a new app, add the chat:write scope under OAuth &amp;amp; Permissions, install it to the workspace and copy the Bot User OAuth Token. Then invite the app to the channel it will post in. Until it is invited, Slack turns the post away.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Make the Airtable token.&lt;/strong&gt; At airtable.com/create/tokens, give a new token the scopes data.records:read and data.records:write and add the client&amp;#39;s base.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fill in the three fields.&lt;/strong&gt; &amp;quot;Slack: Channel&amp;quot; takes a name like #leads or an ID like C0123456789. &amp;quot;Airtable: Base ID&amp;quot; is the appXXXXXXXXXXXXXX code, and &amp;quot;Airtable: Table&amp;quot; is the table&amp;#39;s name.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Write the post.&lt;/strong&gt; The installed text is two lines, &amp;quot;A record is added in Airtable.&amp;quot; and &amp;quot;Added at:&amp;quot; followed by the time Airtable created the row. That tells the team something happened without saying what. Open the Slack step and add the columns they look at first (each column by name, such as &lt;code&gt;{{ trigger.payload.fields.Customer }}&lt;/code&gt; for a Customer column).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Turn it on.&lt;/strong&gt; Thrum looks at the table every 15 minutes and posts once for each row added since its last look, oldest first. Rows that were in the table before you switched it on stay quiet.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;How Thrum treats a bad Slack token&lt;/h2&gt;
&lt;p&gt;Slack can answer a revoked token with a success code and an error tucked inside the reply. Thrum reads the reply, so a dead token fails the step and shows up on the client&amp;#39;s health, where a plain status check would have logged the post as sent. Busy and server errors are tried again at growing waits, up to 3 attempts. A post whose connection dropped mid-request is not repeated automatically, so the channel never gets a double post without you choosing to retry.&lt;/p&gt;
&lt;h2&gt;Other ways the two join in Thrum&lt;/h2&gt;
&lt;p&gt;The same pair can post when a row is changed rather than added. That version asks for a &amp;quot;Last modified time&amp;quot; field in the table and can be limited to one view, such as Ready to quote. In the other direction, each new message in a Slack channel can become an Airtable row, checked every 5 minutes. The Slack side also has &amp;quot;Edit a message&amp;quot;, which updates the bot&amp;#39;s post in place, for example one line per lead that moves from new to booked. The &lt;a href=&quot;https://www.thrum.run/integrations/airtable/slack&quot;&gt;Airtable and Slack page&lt;/a&gt; lists all the combinations with their starters.&lt;/p&gt;
&lt;h2&gt;Choosing between them&lt;/h2&gt;
&lt;p&gt;If the client wants a feed of edits to a base, Airtable&amp;#39;s notification rules cover it with no automation. For one custom message on one base, Airtable&amp;#39;s automation action is close at hand. Thrum earns its place when you run the same alert for many clients and want each one on the client&amp;#39;s own accounts, with retries and an alert when a key stops working.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/docs/receiving-base-activity-notifications-in-slack&quot;&gt;https://support.airtable.com/docs/receiving-base-activity-notifications-in-slack&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/docs/airtable-automation-actions-slack&quot;&gt;https://support.airtable.com/docs/airtable-automation-actions-slack&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/articles/5081141887-airtable-automation-trigger-when-record-created&quot;&gt;https://support.airtable.com/articles/5081141887-airtable-automation-trigger-when-record-created&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/airtable/integrations/slack&quot;&gt;https://zapier.com/apps/airtable/integrations/slack&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to get a Slack message for every new Shopify order</title><link>https://www.thrum.run/blog/slack-message-new-shopify-order</link><guid isPermaLink="true">https://www.thrum.run/blog/slack-message-new-shopify-order</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Post each new Shopify order to a Slack channel with its number, email, total and payment status, using Shopify Flow, Zapier or a Thrum starter per client.</description><content:encoded>&lt;p&gt;Shop owners like to see orders arrive. Their packers want them in one list, and nobody wants to keep the Shopify admin open in a tab all day. A Slack channel that gets a short post per order covers all three. You can build that with Shopify&amp;#39;s own Flow app, with Zapier, or with a Thrum starter that reads the client&amp;#39;s store and posts with the client&amp;#39;s Slack app, and this guide goes through each.&lt;/p&gt;
&lt;h2&gt;Shopify Flow&lt;/h2&gt;
&lt;p&gt;Flow is Shopify&amp;#39;s own automation app. Its listing in the Shopify App Store describes it as free, with workflows to automate marketing, order fulfilment, inventory and fraud checks, hundreds of templates, and connections to tags, metafields, B2B, Slack, Google Sheets and more. If the client&amp;#39;s store is on Shopify and the team only needs order alerts in their Slack, Flow is the first thing to look at, and Shopify&amp;#39;s help centre is the place to set it up. Slack may offer other options too, described in Slack&amp;#39;s help centre.&lt;/p&gt;
&lt;h2&gt;Zapier&lt;/h2&gt;
&lt;p&gt;Zapier&amp;#39;s Shopify and Slack page has templates such as &amp;quot;Share new paid orders from Shopify to Slack&amp;quot; and &amp;quot;Post Slack messages for new paid orders in Shopify&amp;quot;, plus versions for updated orders, refunds, abandoned carts and new customers. On the Shopify side it lists events for a new order and a paid order, among many others, and on the Slack side a channel message.&lt;/p&gt;
&lt;h2&gt;Thrum&lt;/h2&gt;
&lt;p&gt;Thrum installs &amp;quot;Post a message in Slack when a new order comes in in Shopify&amp;quot; into the client&amp;#39;s own workspace. One detail decides whether it fits. The Shopify connection works only for a store that already has a custom app created by the store&amp;#39;s admin, because the token comes from that app.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Install it.&lt;/strong&gt; Under Templates → Library, open the starter and install it into the client. It lands switched off, listing two accounts to connect and one field.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Get the store&amp;#39;s token.&lt;/strong&gt; In the client&amp;#39;s Shopify admin, go to Apps → Develop apps and open their custom app. Its Admin API scopes (the permissions the app holds) must include read_orders for the order events and write_customers for the customer steps. The token is in the app&amp;#39;s settings (Shopify files it under API credentials). Shopify shows it once when it is made, and if it is no longer shown, generate a new one.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Set up the Slack app.&lt;/strong&gt; At api.slack.com/apps in the client&amp;#39;s Slack (where Slack apps are made), create an app, give it the chat:write scope, install it to the workspace and copy the Bot User OAuth Token. Invite the app into the channel you want the orders in.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Choose the channel.&lt;/strong&gt; The one field is &amp;quot;Slack: Channel&amp;quot;, a name such as #orders or an ID like C0123456789.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Read the post before going live.&lt;/strong&gt; Each order produces one post. The first line says a new order has come in, and the lines below give the order number as the shop shows it (#1001 and so on), the customer&amp;#39;s email, the total, the currency and the payment status. The new-order step also carries the customer&amp;#39;s first and last name, the fulfilment status and when the order was placed, so add any of those to the Slack step if the team wants them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Switch it on.&lt;/strong&gt; Thrum checks the store every 5 minutes and posts each order placed since the last check, oldest first. Orders from before the switch is flipped are not posted.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;Paid orders only&lt;/h2&gt;
&lt;p&gt;Some teams only want to start packing once money has arrived. For them, install &amp;quot;Post a message in Slack when an order is paid in Shopify&amp;quot; in its place. It also checks every 5 minutes, fires once per order however often the order is edited afterwards, and sends the same lines with &amp;quot;An order is paid in Shopify.&amp;quot; on top.&lt;/p&gt;
&lt;h2&gt;Keeping one post per order&lt;/h2&gt;
&lt;p&gt;The channel never gets the same order twice by accident. Each order has an identity in Thrum, so overlapping checks start nothing new. If Slack is busy or failing, the post is retried at waits starting from 5 seconds, up to 3 attempts. If the connection drops after Slack got the request, the post is held for you to retry by hand once you have looked at the channel.&lt;/p&gt;
&lt;h2&gt;Spotting a broken connection&lt;/h2&gt;
&lt;p&gt;Two things go wrong with stores over time. The custom app&amp;#39;s token can be replaced in Shopify, and a Slack app can be removed from the workspace. Slack sometimes reports a dead token with a success code and an error inside the reply, and Thrum reads that reply and fails the step. A refused Shopify check is kept and raised as an alert that names the app, so you hear about it from Thrum rather than from a client asking why the channel went quiet.&lt;/p&gt;
&lt;p&gt;The other ways the two apps work together are on the &lt;a href=&quot;https://www.thrum.run/integrations/shopify/slack&quot;&gt;Shopify and Slack page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://apps.shopify.com/flow&quot;&gt;https://apps.shopify.com/flow&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/shopify/integrations/slack&quot;&gt;https://zapier.com/apps/shopify/integrations/slack&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to send an SMS when an Airtable record is created</title><link>https://www.thrum.run/blog/sms-new-airtable-record</link><guid isPermaLink="true">https://www.thrum.run/blog/sms-new-airtable-record</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Text a customer or the owner when a row lands in a client's Airtable base, from the client's own Twilio number, with Zapier, a script, or a Thrum workflow.</description><content:encoded>&lt;p&gt;Some people see a text long before they open an email, such as a plumber who is out on a job when a booking lands, or the customer who made that booking and wants to know it arrived. If the bookings live in Airtable, this guide shows how to send that text automatically. Thrum builds it from Airtable&amp;#39;s &amp;quot;A record is added&amp;quot; and its built-in Text step on the client&amp;#39;s own Twilio account, and two other routes are covered first.&lt;/p&gt;
&lt;h2&gt;Zapier with Twilio&lt;/h2&gt;
&lt;p&gt;Zapier pairs the two directly. Its Airtable and Twilio page lists templates including &amp;quot;Send SMS messages via Twilio for new Airtable records&amp;quot; and &amp;quot;Send Twilio SMS messages with new Airtable records in view&amp;quot;, built on Twilio&amp;#39;s action that sends an SMS to one or more numbers. The Airtable &amp;quot;New Record&amp;quot; event covers new records and records the first time they enter a chosen view, and Zapier&amp;#39;s Free plan checks for new data every 15 minutes.&lt;/p&gt;
&lt;h2&gt;A script in Airtable&lt;/h2&gt;
&lt;p&gt;Airtable&amp;#39;s automations have no general action for calling another service. Airtable&amp;#39;s help centre sends you to &amp;quot;Run a script&amp;quot; for that, with fetch() inside the script and the key kept in Secrets. A run can make up to 50 fetch requests and each one times out after 30 seconds. Writing the request itself is up to you, and Twilio may also publish other approaches, so Twilio&amp;#39;s documentation is the place to start.&lt;/p&gt;
&lt;p&gt;Whatever sends the text, Airtable&amp;#39;s notes about &amp;quot;When record created&amp;quot; are worth knowing. It only acts on records created after the automation is on, and a record someone is typing by hand will likely set it off before they finish. Airtable suggests &amp;quot;When record matches conditions&amp;quot; or &amp;quot;When record enters view&amp;quot; for hand-entered rows.&lt;/p&gt;
&lt;h2&gt;Building it in Thrum&lt;/h2&gt;
&lt;p&gt;This pair has no starter in the library, so you build the workflow on the canvas from two steps.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Start a workflow for the client.&lt;/strong&gt; Create a new workflow in the client&amp;#39;s workspace and choose Airtable&amp;#39;s &amp;quot;A record is added&amp;quot; as the step that starts it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Point it at the table.&lt;/strong&gt; Fill in the Base ID (the appXXXXXXXXXXXXXX code) and the table&amp;#39;s name, then choose the client&amp;#39;s Airtable token. Make the token at airtable.com/create/tokens with data.records:read and data.records:write and give it the client&amp;#39;s base.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Add the Text step.&lt;/strong&gt; From the add-step menu, under Send, add the Text step. Leave &amp;quot;Send&amp;quot; on the Twilio option and pick the client&amp;#39;s Twilio account under &amp;quot;Send with&amp;quot;. That account needs three things from the Twilio console, the Account SID, the auth token and the number to send from, so the text arrives from the client&amp;#39;s own number.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fill in To and Message.&lt;/strong&gt; For a text to the customer, set To to the phone column of the new row (&lt;code&gt;{{ trigger.payload.fields.Phone }}&lt;/code&gt; for a column called Phone). For an alert to the owner, type the owner&amp;#39;s mobile number instead. Write the message with the columns it should mention, for example the customer&amp;#39;s first name and the time they asked for.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Publish and switch it on.&lt;/strong&gt; The canvas now shows the Airtable step joined to the Text step. Thrum reads the table every 15 minutes and sends one text per row added since the previous read, oldest first. Rows that were there before the workflow went live are not texted.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;Texting when a row reaches a stage&lt;/h2&gt;
&lt;p&gt;To text when a job is confirmed rather than when it is first entered, use &amp;quot;A record is changed&amp;quot; as the starting step. The table needs a field of the type &amp;quot;Last modified time&amp;quot;, ideally limited to the columns that matter, and you give its name in the step. Add a view name as well, for example Ready to quote, and the workflow only acts on rows in that view, which reads as &amp;quot;a record enters Ready to quote&amp;quot;.&lt;/p&gt;
&lt;h2&gt;When there is no number&lt;/h2&gt;
&lt;p&gt;Some rows arrive without a phone number. The Text step does not fail in that case. It sends nothing, the run carries on with any later steps, and the run&amp;#39;s timeline says &amp;quot;Sent nothing&amp;quot; with the step&amp;#39;s name and the place it looked for the number. You can see at a glance which bookings need a number added by hand.&lt;/p&gt;
&lt;h2&gt;When Twilio refuses or is slow&lt;/h2&gt;
&lt;p&gt;A server error or a request to slow down from Twilio is tried again, first after 5 seconds and then at doubling waits, up to 3 attempts. A refusal of any other kind fails the step at once, because sending the same request again would get the same answer. If the connection drops after Twilio has the request, Thrum leaves the retry to you so the customer is not texted twice.&lt;/p&gt;
&lt;h2&gt;Which route fits&lt;/h2&gt;
&lt;p&gt;Zapier covers the pair with ready templates on a Zapier account. A script keeps everything inside Airtable but needs someone to write and look after the code. Thrum suits the agency or freelancer who runs this kind of alert for many clients, each texting from their own Twilio number, with every send and skipped send visible in the run history. The &lt;a href=&quot;https://www.thrum.run/integrations/airtable/twilio&quot;&gt;Airtable and Twilio page&lt;/a&gt; shows both Airtable starting steps with the Text step.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/airtable/integrations/twilio&quot;&gt;https://zapier.com/apps/airtable/integrations/twilio&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/docs/run-a-script-action&quot;&gt;https://support.airtable.com/docs/run-a-script-action&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/articles/5081141887-airtable-automation-trigger-when-record-created&quot;&gt;https://support.airtable.com/articles/5081141887-airtable-automation-trigger-when-record-created&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to send a Telegram message when an Airtable record is added</title><link>https://www.thrum.run/blog/telegram-message-new-airtable-record</link><guid isPermaLink="true">https://www.thrum.run/blog/telegram-message-new-airtable-record</guid><pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate><description>Have a Telegram bot post into a client's group or channel whenever their Airtable table gains a row, set up with Zapier or with a Thrum starter in six steps.</description><content:encoded>&lt;p&gt;Where a client&amp;#39;s staff talk in a Telegram group, a bot in that group is the shortest path from &amp;quot;a new order is in the base&amp;quot; to &amp;quot;someone is on it&amp;quot;. This guide sets up a bot message for every new Airtable row. It covers Zapier&amp;#39;s version briefly and spends most of its length on Thrum, where the bot belongs to the client and the message goes out within one 15-minute check of the table.&lt;/p&gt;
&lt;h2&gt;Before you start, whichever tool you use&lt;/h2&gt;
&lt;p&gt;You need a Telegram bot. In Telegram, message @BotFather, send /newbot, follow its questions and copy the token it gives you. Treat the token like a password. Then either add the bot to the client&amp;#39;s group, or have the person who should receive the messages send the bot one message first, since the bot writes only to chats it is part of.&lt;/p&gt;
&lt;p&gt;Telegram may offer other ways to do this through its own bot tools, and Telegram&amp;#39;s bot documentation is the place to read about them. Inside Airtable, Airtable&amp;#39;s help centre sends calls to outside services through the &amp;quot;Run a script&amp;quot; action, which means writing and maintaining code.&lt;/p&gt;
&lt;h2&gt;With Zapier&lt;/h2&gt;
&lt;p&gt;Zapier&amp;#39;s Airtable and Telegram page offers &amp;quot;Send messages in Telegram for new records in Airtable&amp;quot; and a version for new or updated records. Its Telegram action sends a message from your bot, and Zapier also has a Telegram event that starts instantly when your bot receives a message, for the reverse direction. The Airtable &amp;quot;New Record&amp;quot; event handles new records and records the first time they enter a chosen view. Zapier&amp;#39;s Free plan checks for new data every 15 minutes.&lt;/p&gt;
&lt;h2&gt;With Thrum&lt;/h2&gt;
&lt;p&gt;Thrum&amp;#39;s starter is &amp;quot;Send a message in Telegram when a record is added in Airtable&amp;quot;. It reads the client&amp;#39;s base with the client&amp;#39;s token and sends with the client&amp;#39;s bot, inside that client&amp;#39;s own workspace.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Install the starter.&lt;/strong&gt; Templates → Library, open the starter, pick the client, install. You get the workflow switched off plus a checklist of two accounts and three fields.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect the bot.&lt;/strong&gt; Paste the token from @BotFather as the client&amp;#39;s Telegram connection. Thrum stores it encrypted with the client&amp;#39;s other keys.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect Airtable.&lt;/strong&gt; Create a token at airtable.com/create/tokens with data.records:read and data.records:write, and add the client&amp;#39;s base to its access list.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fill in the Chat ID.&lt;/strong&gt; &amp;quot;Telegram: Chat ID&amp;quot; is where the bot writes. For a group, it is a number such as -1001234567890. For a public channel, it can be its @name. The bot has to be a member of that group or channel.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fill in the base and table.&lt;/strong&gt; &amp;quot;Airtable: Base ID&amp;quot; is the appXXXXXXXXXXXXXX code, and &amp;quot;Airtable: Table&amp;quot; is the table to watch, for example Leads.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Write a message worth reading, then switch it on.&lt;/strong&gt; As installed, the bot sends two lines, &amp;quot;A record is added in Airtable.&amp;quot; and &amp;quot;Added at:&amp;quot; followed by the row&amp;#39;s creation time. Change them in the Telegram step to the columns the team needs (&lt;code&gt;{{ trigger.payload.fields.Address }}&lt;/code&gt; brings in a column called Address). Once switched on, Thrum checks the table every 15 minutes and sends one message per new row, oldest first, leaving out rows that were already there.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;Photos and files&lt;/h2&gt;
&lt;p&gt;Telegram has two more steps in Thrum. &amp;quot;Send a photo&amp;quot; sends a picture from a web address, and &amp;quot;Send a file&amp;quot; sends a PDF, an invoice or a report the same way. Each takes files up to 4.5 MB with an optional caption. Pointing either at a link from an earlier step lets the bot share a quote or a job photo alongside the alert.&lt;/p&gt;
&lt;h2&gt;When a row changes instead&lt;/h2&gt;
&lt;p&gt;For alerts about progress, such as a delivery marked out, use &amp;quot;Send a message in Telegram when a record is changed in Airtable&amp;quot;. It needs a field of the type &amp;quot;Last modified time&amp;quot; in the table, named in the starter, and it can be narrowed to rows in one view. Like the first, it checks every 15 minutes.&lt;/p&gt;
&lt;h2&gt;Messages to the bot, saved in Airtable&lt;/h2&gt;
&lt;p&gt;The pair works the other way too. With &amp;quot;Create a record in Airtable when a message is sent to the bot in Telegram&amp;quot;, each message reaches Thrum within seconds and becomes a row holding the text, the sender&amp;#39;s first name, the group&amp;#39;s name and whether the chat is private or a group. Two rules come with it. A bot sends its incoming messages to one place, so only one workflow can listen per bot, and no other tool can use that bot&amp;#39;s updates at the same time. In a group, the bot sees only commands, replies and mentions unless privacy mode is switched off in BotFather.&lt;/p&gt;
&lt;h2&gt;If Telegram says no&lt;/h2&gt;
&lt;p&gt;A busy or failing Telegram is retried after 5 seconds and then at doubling waits, up to 3 attempts. Any other refusal fails the step straight away, so check the Chat ID and that the bot is in the group. If a message may have gone out before the connection dropped, Thrum leaves the retry to you so the group does not see it twice.&lt;/p&gt;
&lt;p&gt;All the ways the two apps join are on the &lt;a href=&quot;https://www.thrum.run/integrations/airtable/telegram&quot;&gt;Airtable and Telegram page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Checked on 14 November 2026.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/apps/airtable/integrations/telegram&quot;&gt;https://zapier.com/apps/airtable/integrations/telegram&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.airtable.com/docs/run-a-script-action&quot;&gt;https://support.airtable.com/docs/run-a-script-action&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to use AI in client automations without it going wrong</title><link>https://www.thrum.run/blog/ai-automation-done-right</link><guid isPermaLink="true">https://www.thrum.run/blog/ai-automation-done-right</guid><pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate><description>Three patterns for AI in small-business automations. Let AI read and sort, let the business's own words reply, and have a person approve anything AI writes.</description><content:encoded>&lt;p&gt;Thrum lets you put an AI step, in beta, into any workflow you run for a client, so we spend a lot of time on how AI automations go wrong for small businesses. The best-known failures have one thing in common, which is that the AI was allowed to talk to customers by itself. It made up a price, promised a time nobody agreed to, or invented a policy, and the business paid for it.&lt;/p&gt;
&lt;p&gt;This post covers the patterns we recommend: let AI read and sort, let the business&amp;#39;s own words do the talking, and put a person in front of anything AI writes to a customer. It also shows how to test an AI step before a real customer sees it, and how Thrum keeps watching it afterwards.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/illustrations/i3-ai-reads.png&quot; alt=&quot;The illustration shows two patterns. On the left, an AI step reads a customer&amp;#39;s text and answers one question, urgent or routine, and the customer gets a message the business wrote in advance. On the right, an AI drafts a reply and an approval step waits for a person before anything is sent.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 1: The safe default on the left, and the approval pattern on the right, both as they work in Thrum.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;What AI is good at in small businesses&lt;/h2&gt;
&lt;p&gt;AI is very good at reading messy messages. Customers do not fill in forms neatly. They write &amp;quot;boiler banging no hot water can u come 2day&amp;quot; in the box marked &amp;quot;Address&amp;quot;. A person can still understand that, and so can a good AI model.&lt;/p&gt;
&lt;p&gt;That makes AI useful for three jobs.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Sorting.&lt;/strong&gt; Is this urgent or routine? A new customer or an existing one? A complaint or a question?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Pulling out details.&lt;/strong&gt; The name, the postcode, the date they want, the kind of job.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Summing up for the owner.&lt;/strong&gt; One line instead of a long email: &amp;quot;New customer, leaking boiler, wants someone today.&amp;quot;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In each of these, the AI&amp;#39;s answer goes to the workflow or to the owner, and never straight to the customer.&lt;/p&gt;
&lt;h2&gt;What AI is bad at&lt;/h2&gt;
&lt;p&gt;AI is bad at facts it was not given. Ask it what a boiler service costs, and if it does not know, it may still give an answer. It will sound confident, and it may be wrong.&lt;/p&gt;
&lt;p&gt;This has already cost real companies. In February 2024, a Canadian tribunal ordered Air Canada to compensate a customer after its website chatbot wrongly told him he could claim a bereavement discount after travelling. The tribunal said it makes no difference whether wrong information comes from a page on the website or from a chatbot. OWASP, a security group, now cites the case in its guidance on AI that states false things. In April 2025, an AI support bot at the software company Cursor told customers about a login rule that did not exist, and some users said they were cancelling their subscriptions.&lt;/p&gt;
&lt;p&gt;So there is a short list of things AI should never decide alone in a client&amp;#39;s business.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;prices&lt;/li&gt;
&lt;li&gt;appointment times&lt;/li&gt;
&lt;li&gt;refunds and policies&lt;/li&gt;
&lt;li&gt;medical or legal advice&lt;/li&gt;
&lt;li&gt;anything the business would have to sign&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Start with the simplest thing that works&lt;/h2&gt;
&lt;p&gt;Anthropic, the company behind the Claude models, published practical advice for building with AI. In short, find the simplest solution that works, and only add complexity when you need it. As it puts it, &amp;quot;This might mean not building agentic systems at all.&amp;quot;&lt;/p&gt;
&lt;p&gt;The advice separates two approaches.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Workflows:&lt;/strong&gt; fixed steps that use AI at certain points.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agents:&lt;/strong&gt; the AI decides its own steps as it goes.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For well-defined jobs, like answering enquiries for a plumber, a workflow is more predictable. Predictable is what a small business owner needs, a system that does the same right thing every time.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; a workflow is a set of fixed steps you can see. The AI step is one step among them, and the path a run takes is always visible.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g6-canvas-run.gif&quot; alt=&quot;Thrum&amp;#39;s canvas shows Lead Rescue as one run moves through its fixed steps, from the form arriving to an instant reply, an email, an Emergency? check that takes the urgent branch, a text to the owner and a wait. A panel lists each step in plain words.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 2: A workflow in Thrum is fixed steps you can see. An AI step slots in as one of them, for example to decide the Emergency? check. Simplified illustration.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Pattern 1: AI reads, your words reply&lt;/h2&gt;
&lt;p&gt;This is the safe default.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A customer sends a message through the form.&lt;/li&gt;
&lt;li&gt;The AI step reads it and answers one question only, urgent or routine.&lt;/li&gt;
&lt;li&gt;A yes/no step picks the matching message.&lt;/li&gt;
&lt;li&gt;The customer gets words the business wrote and approved in advance.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The customer gets a fast, relevant reply, and the AI never writes a word they see. If it sorts something wrongly, the worst case is that a routine message goes out instead of an urgent one, and the owner still gets the details.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; the AI step, which is in beta, works with Anthropic&amp;#39;s Claude, OpenAI, OpenRouter or Groq. You choose the model and write its instructions. You can give it a short list of app steps it is allowed to use, and nothing else. Each AI step is capped at 8 calls to the model and 12 uses of those app steps, so one confused run cannot loop or run up a bill.&lt;/p&gt;
&lt;h2&gt;Pattern 2: AI drafts, a person approves&lt;/h2&gt;
&lt;p&gt;Sometimes a pre-written message is not enough. A customer asks a specific question, and a tailored reply would win the job.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The AI drafts a reply. Its instructions say what the business offers and tell it never to give prices or times.&lt;/li&gt;
&lt;li&gt;An approval step pauses the workflow.&lt;/li&gt;
&lt;li&gt;Nothing reaches the customer until a person says yes.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; the approval step, which is in beta, stops the run and asks the people you name. They can decide on the run screen, in the client&amp;#39;s portal or from an emailed link with a six-digit code. The first decision wins, and the run carries on once.&lt;/p&gt;
&lt;h2&gt;Pattern 3: AI writes only for the owner&lt;/h2&gt;
&lt;p&gt;This is the lowest-risk use of AI, and often the most appreciated. The AI turns each enquiry into one line for the owner:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;New customer, Sam, boiler leaking under the stairs, wants someone today. Mobile 07700 900123.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The owner reads it between jobs. If the summary is slightly off, nothing bad happens, because the owner calls the customer anyway.&lt;/p&gt;
&lt;h2&gt;Test it before a customer sees it&lt;/h2&gt;
&lt;p&gt;Never switch on an AI step on the strength of three test messages.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Collect 20 real past messages&lt;/strong&gt; from the business. Remove names and phone numbers first, and get the owner&amp;#39;s permission before sending customer messages to an AI provider.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Run every one through the AI step&lt;/strong&gt; and write down what it decided.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Check each answer by hand.&lt;/strong&gt; If more than one or two are wrong, rewrite the instructions and run all 20 again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Decide what happens when the AI is unsure.&lt;/strong&gt; The safe choice is to treat it as routine and send the details to the owner.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Keep the instructions short and specific.&lt;/strong&gt; &amp;quot;Answer only urgent or routine&amp;quot; beats a page of rules.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; use Test run on the canvas to try the workflow and see every step&amp;#39;s result before you publish.&lt;/p&gt;
&lt;h2&gt;Watch it after it goes live&lt;/h2&gt;
&lt;p&gt;AI steps fail in ways ordinary steps do not. The AI provider can be slow, an account can run out of credit, or the provider can have a bad hour. Your client will not tell you, because the first sign is customers who stop getting replies.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; each workflow is watched, including its AI steps. Three failures in a row, a fifth of recent runs failing, or runs taking three times longer than usual moves a workflow to &lt;strong&gt;Degraded&lt;/strong&gt;. If it goes quiet for three times its usual gap, it moves to &lt;strong&gt;Stopped&lt;/strong&gt; and you get an email. The alert goes to you, never to your client.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g2-silence-to-alert.gif&quot; alt=&quot;A client&amp;#39;s workflow goes quiet overnight, moves to Stopped and rises to the top of the list, the alert email arrives, and after the fix it is Thrumming again with a recovery email.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 3: You hear first, you fix it, and you hear when it is back. Example clients.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Let AI read and sort. Let the business&amp;#39;s approved words reply.&lt;/li&gt;
&lt;li&gt;If AI writes to a customer, a person approves it first. In Thrum that is the approval step.&lt;/li&gt;
&lt;li&gt;Never let AI decide prices, times, policies, or medical or legal questions.&lt;/li&gt;
&lt;li&gt;Test on 20 real messages, decide what happens when it is unsure, and keep watching it after launch.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Anthropic, &amp;quot;Building effective agents&amp;quot; (December 2024): &lt;a href=&quot;https://www.anthropic.com/engineering/building-effective-agents&quot;&gt;https://www.anthropic.com/engineering/building-effective-agents&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Moffatt v. Air Canada, 2024 BCCRT 149, summary: &lt;a href=&quot;https://www.mccarthy.ca/en/insights/blogs/techlex/moffatt-v-air-canada-misrepresentation-ai-chatbot&quot;&gt;https://www.mccarthy.ca/en/insights/blogs/techlex/moffatt-v-air-canada-misrepresentation-ai-chatbot&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;AI Incident Database, Cursor support bot (April 2025): &lt;a href=&quot;https://incidentdatabase.ai/cite/1039/&quot;&gt;https://incidentdatabase.ai/cite/1039/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;OWASP Top 10 for LLM Applications, LLM09 Misinformation: &lt;a href=&quot;https://owasp.github.io/www-project-top-10-for-large-language-model-applications/2_0_vulns/LLM09_Misinformation.html&quot;&gt;https://owasp.github.io/www-project-top-10-for-large-language-model-applications/2_0_vulns/LLM09_Misinformation.html&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>7 automations small businesses pay for</title><link>https://www.thrum.run/blog/automations-small-businesses-pay-for</link><guid isPermaLink="true">https://www.thrum.run/blog/automations-small-businesses-pay-for</guid><pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate><description>Seven automations that fix a weekly cost for a small business, from instant lead replies to failed payment chases, with their steps, catches and texting rules.</description><content:encoded>&lt;p&gt;Small business owners pay to stop losing customers, chasing money and filling empty appointment slots by hand. Each automation below fixes one of those, and six of the seven are a handful of steps you can build in Thrum.&lt;/p&gt;
&lt;p&gt;For each one we cover what it fixes, the steps, how the owner sees it working, what to watch out for, and how it is set up in Thrum. Start with the one that hurts your client most.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/illustrations/i6-seven-automations.png&quot; alt=&quot;Seven automation cards each show what starts the automation, its steps and the result, for a missed-call text back, an instant lead reply, appointment reminders, review requests, a quote follow-up, an unpaid invoice chase and a rebooking nudge.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 1: Seven automations, each a handful of steps.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A quick word on terms. A &lt;strong&gt;workflow&lt;/strong&gt; is a set of steps that runs by itself. It &lt;strong&gt;starts&lt;/strong&gt; when something happens, such as a form being sent, a payment failing or a set time arriving.&lt;/p&gt;
&lt;h2&gt;1. Missed-call text back&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;What it fixes:&lt;/strong&gt; calls missed while the owner is on a job. Many callers will not leave a voicemail. They ring the next business on the list.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The steps:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A call goes unanswered.&lt;/li&gt;
&lt;li&gt;The caller gets a text: &amp;quot;Sorry we missed you. How can we help?&amp;quot;&lt;/li&gt;
&lt;li&gt;The owner gets a text with the caller&amp;#39;s number, so someone can call back.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;How the owner sees it:&lt;/strong&gt; a text for each missed call, with the caller&amp;#39;s number, so nothing slips.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Watch out for:&lt;/strong&gt; landlines. A text to a landline goes nowhere, so the owner still needs the number to call back.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; this is the one automation here that Thrum does not run, because Thrum does not handle phone calls and so cannot tell when one is missed. Build it in the client&amp;#39;s phone system, if it offers a missed-call text.&lt;/p&gt;
&lt;h2&gt;2. Instant lead reply&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;What it fixes:&lt;/strong&gt; slow replies to website enquiries. People who contact a business online often ask several at once, and the first to reply often wins. A 2011 Harvard Business Review analysis of 1.25 million leads found that firms that tried to reach a lead within an hour were nearly seven times as likely to have a real conversation as those who tried even an hour later.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The steps:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The customer gets a text, and an email if they gave one, within about a minute. Texts wait out the night, so an enquiry sent between 21:00 and 08:00 is answered at 08:00.&lt;/li&gt;
&lt;li&gt;If the message has an urgent word in it (&amp;quot;leak&amp;quot;, &amp;quot;burst&amp;quot;, &amp;quot;no heat&amp;quot;), the owner&amp;#39;s phone gets a text with the details.&lt;/li&gt;
&lt;li&gt;If nobody marks it contacted within 10 minutes, the text goes to a backup number, if you set one.&lt;/li&gt;
&lt;li&gt;Anyone not contacted within an hour gets a friendly text with a booking link.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;img src=&quot;../images/illustrations/i1-the-whole-flow.png&quot; alt=&quot;The illustration follows one enquiry from the form to the reply 52 seconds later, the owner&amp;#39;s alert about an urgent word, the owner&amp;#39;s portal and the monthly report.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 2: Instant lead reply, from the form to the owner&amp;#39;s report. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;How the owner sees it:&lt;/strong&gt; each enquiry, and how fast it was answered, on their phone.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Watch out for:&lt;/strong&gt; the urgent words. Agree them with the owner, and keep the list short. Too many, and all enquiries look like emergencies.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; this one comes ready-made as the Lead Rescue template. You fill in five details for each client: business name, owner&amp;#39;s mobile, owner&amp;#39;s email, urgent words and booking link.&lt;/p&gt;
&lt;h2&gt;3. Appointment reminders&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;What it fixes:&lt;/strong&gt; people who forget their appointment, leaving an empty slot nobody can fill.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The steps:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Someone books.&lt;/li&gt;
&lt;li&gt;The workflow waits until the day before.&lt;/li&gt;
&lt;li&gt;It sends a text: &amp;quot;See you tomorrow at 10. Reply to change the time.&amp;quot;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;How the owner sees it:&lt;/strong&gt; reminders sent this month, in the monthly report.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Watch out for:&lt;/strong&gt; changes. Check what the booking app sends when someone moves a booking, so a reminder never goes out for the old time.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; it can start when &amp;quot;Someone books a meeting&amp;quot; in Calendly, or when a new booking comes in through Square.&lt;/p&gt;
&lt;h2&gt;4. Review requests&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;What it fixes:&lt;/strong&gt; happy customers who never leave a review because nobody asked at the right moment.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The steps:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A job is marked done.&lt;/li&gt;
&lt;li&gt;The workflow waits two hours.&lt;/li&gt;
&lt;li&gt;It sends a text: &amp;quot;Thanks for choosing us. Would you leave a review?&amp;quot; with the link.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;How the owner sees it:&lt;/strong&gt; requests sent, next to the reviews they can see coming in.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Watch out for:&lt;/strong&gt; picking who to ask. Ask each customer once the job is done. If something went wrong, fix it first, but do not filter who gets asked, because Google&amp;#39;s review rules do not allow that.&lt;/p&gt;
&lt;h2&gt;5. Quote follow-up&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;What it fixes:&lt;/strong&gt; quotes that go quiet. The customer meant to reply and forgot.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The steps:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A quote request comes in through the form.&lt;/li&gt;
&lt;li&gt;The workflow waits two days.&lt;/li&gt;
&lt;li&gt;A yes/no step checks whether they have booked.&lt;/li&gt;
&lt;li&gt;If not, it sends a text: &amp;quot;Any questions about your quote?&amp;quot;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;How the owner sees it:&lt;/strong&gt; follow-ups sent, and which of those people booked.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Watch out for:&lt;/strong&gt; nagging. One friendly nudge is helpful. Three is a reason to block the number.&lt;/p&gt;
&lt;h2&gt;6. Failed payment chase&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;What it fixes:&lt;/strong&gt; owners spending evenings chasing money.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The steps:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A card payment fails.&lt;/li&gt;
&lt;li&gt;The customer gets an email with a link to pay again.&lt;/li&gt;
&lt;li&gt;The workflow waits three days.&lt;/li&gt;
&lt;li&gt;If it is still unpaid, a polite reminder goes out.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;How the owner sees it:&lt;/strong&gt; fewer awkward phone calls, and payments arriving without them asking.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Watch out for:&lt;/strong&gt; tone. Many failed payments come from an expired or replaced card, so write it as a friendly note about the card.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; it starts when Stripe reports &amp;quot;A payment fails&amp;quot;, and a step makes the payment link.&lt;/p&gt;
&lt;h2&gt;7. Rebooking nudge&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;What it fixes:&lt;/strong&gt; regular customers who drift away. Salons, vets, dentists and garages all depend on people coming back on time.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The steps:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Every Monday morning, the workflow starts by itself.&lt;/li&gt;
&lt;li&gt;It finds customers whose last visit was long enough ago, from the business&amp;#39;s booking app or customer list.&lt;/li&gt;
&lt;li&gt;It sends each one a text: &amp;quot;It is time for your next appointment.&amp;quot;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;How the owner sees it:&lt;/strong&gt; rebookings that happened without anyone picking up the phone.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Watch out for:&lt;/strong&gt; people who have moved on. Include an easy way to say &amp;quot;no thanks&amp;quot;, and stop texting them when they do.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; a schedule starts it weekly, at a time in the client&amp;#39;s own time zone.&lt;/p&gt;
&lt;h2&gt;Before you switch any of these on&lt;/h2&gt;
&lt;p&gt;Six of the seven send texts. If the business is in the US and texts from a normal local phone number, three rules apply.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Register the number first.&lt;/strong&gt; This is called A2P 10DLC registration. Since September 2023, Twilio blocks texts from unregistered local numbers to US phones, and checks take about 7 business days, or up to 10 when Twilio is busy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Only text people who asked to hear from the business,&lt;/strong&gt; for example by filling in the form. For missed-call texts, check with a lawyer whether a call counts as consent. Review requests and rebooking texts may count as marketing, which needs stronger, written consent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Let people reply STOP.&lt;/strong&gt; Twilio handles STOP and similar words by default. Stop texting them when they do.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;None of this is legal advice. Use it as a list of what to check before a client&amp;#39;s first text goes out.&lt;/p&gt;
&lt;h2&gt;How these are built in Thrum&lt;/h2&gt;
&lt;p&gt;Every automation above except the missed-call text is built from the same small set of steps, which are texts, emails, waits, yes/no checks and app steps in apps such as Calendly, Square, Stripe, HubSpot and Google Sheets. Lead Rescue comes ready-made. You build the others once on the canvas, save them as templates, and reuse them for each client.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g6-canvas-run.gif&quot; alt=&quot;Thrum&amp;#39;s canvas shows Lead Rescue. One run moves through it step by step, the used branch turns green and the other is skipped, and a panel lists each step in plain words.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 3: Building and watching a workflow on Thrum&amp;#39;s canvas. Simplified illustration using Lead Rescue&amp;#39;s own wording for each step.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Thrum then does the part that keeps the client paying.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;It watches every workflow.&lt;/strong&gt; If one goes quiet or starts failing, you hear first. Your client is not told.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;It shows the client the results&lt;/strong&gt; in a portal in their colours, which on Agency and Scale can sit on your web address or theirs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;It sums up the month&lt;/strong&gt; on the 1st, on one page.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Forms are live today, and the rest of Thrum is built and not yet used by any customer.&lt;/p&gt;
&lt;h2&gt;Which one to sell first&lt;/h2&gt;
&lt;p&gt;Ask the owner one question: &amp;quot;Where do you lose customers or money every week?&amp;quot;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&amp;quot;We miss calls on jobs.&amp;quot;&lt;/strong&gt; Sell number 1.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&amp;quot;People fill in the form and go elsewhere.&amp;quot;&lt;/strong&gt; Sell number 2.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&amp;quot;No-shows.&amp;quot;&lt;/strong&gt; Sell number 3.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&amp;quot;We have hardly any reviews.&amp;quot;&lt;/strong&gt; Sell number 4.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Sell one, show it working for a month, then offer the next. A client who can see the first one working is the easiest person to sell the second one to.&lt;/p&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Each automation fixes one weekly cost: missed calls, slow replies, no-shows, few reviews, cold quotes, unpaid invoices, lapsed regulars.&lt;/li&gt;
&lt;li&gt;Each is a handful of steps. In Thrum, Lead Rescue is ready-made, and the others, apart from the missed-call text, are built once and reused as templates.&lt;/li&gt;
&lt;li&gt;Check the texting rules before the first text goes out.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Solo is $20 a seat a month, and each seat carries one client. Every account starts with a 14-day trial for two clients, with no card.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Twilio, A2P 10DLC: &lt;a href=&quot;https://www.twilio.com/docs/messaging/compliance/a2p-10dlc&quot;&gt;https://www.twilio.com/docs/messaging/compliance/a2p-10dlc&lt;/a&gt; and &lt;a href=&quot;https://support.twilio.com/hc/en-us/articles/1260800720410-What-is-A2P-10DLC&quot;&gt;https://support.twilio.com/hc/en-us/articles/1260800720410-What-is-A2P-10DLC&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Twilio, full blocking of unregistered traffic: &lt;a href=&quot;https://www.twilio.com/en-us/changelog/-u-s--a2p-10dlc--full-blocking-of-traffic-sent-from-unregistered&quot;&gt;https://www.twilio.com/en-us/changelog/-u-s--a2p-10dlc--full-blocking-of-traffic-sent-from-unregistered&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Twilio, opt-out keywords: &lt;a href=&quot;https://www.twilio.com/en-us/blog/insights/best-practices/update-to-fcc-s-sms-opt-out-keywords&quot;&gt;https://www.twilio.com/en-us/blog/insights/best-practices/update-to-fcc-s-sms-opt-out-keywords&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;47 CFR 64.1200 (TCPA rules): &lt;a href=&quot;https://www.ecfr.gov/current/title-47/section-64.1200&quot;&gt;https://www.ecfr.gov/current/title-47/section-64.1200&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Oldroyd, McElheran and Elkington, &amp;quot;The Short Life of Online Sales Leads&amp;quot;, Harvard Business Review, March 2011: &lt;a href=&quot;https://hbr.org/2011/03/the-short-life-of-online-sales-leads&quot;&gt;https://hbr.org/2011/03/the-short-life-of-online-sales-leads&lt;/a&gt; (figures as quoted in &lt;a href=&quot;https://customerthink.com/how_fast_are_you/&quot;&gt;https://customerthink.com/how_fast_are_you/&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to impress clients with automation (and keep them paying every month)</title><link>https://www.thrum.run/blog/impress-clients-with-automation</link><guid isPermaLink="true">https://www.thrum.run/blog/impress-clients-with-automation</guid><pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate><description>The three kinds of proof that keep automation clients paying each month, from a portal they can check to a monthly report and problems fixed before they notice.</description><content:encoded>&lt;p&gt;Your clients cannot see the automation itself, and most of them do not want to. They are impressed by proof that their customers were looked after, that problems were fixed before they noticed, and that someone sent them a clear summary each month.&lt;/p&gt;
&lt;p&gt;Thrum is built to produce exactly that proof. This post explains the three kinds of proof that keep clients paying, how Thrum delivers each one, and the small habits that make the difference. The ideas work with any tool. The screens are Thrum&amp;#39;s.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/illustrations/i4-what-clients-see.png&quot; alt=&quot;On the left, a technical run log with codes is captioned &amp;quot;evidence for you&amp;quot;. On the right, a plain summary reading &amp;quot;36 people got in touch. 25 heard back in under 2 minutes&amp;quot; is captioned &amp;quot;evidence for them&amp;quot;. Below them are three labels, proof of work, proof of value and proof you were watching.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 1: What often gets sent, and what the owner needs to see. Both are true, and the plain summary is the one that gets the monthly fee renewed.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Why &amp;quot;it works&amp;quot; is not enough&lt;/h2&gt;
&lt;p&gt;When an automation works well, nothing happens that the owner notices. The customer got a text in a minute, and the review request went out the day after the job. None of it crossed the owner&amp;#39;s desk.&lt;/p&gt;
&lt;p&gt;That is good work. It is also invisible work, and invisible work is easy to cut. When the owner goes through monthly costs, all the other lines are things they can picture. Yours is &amp;quot;the automation thing&amp;quot;.&lt;/p&gt;
&lt;p&gt;A common mistake is sending a screenshot of the tool, or a list of codes and green ticks. That proves something to you, and to a plumber it is a page of codes. He wants to know whether his customers got looked after.&lt;/p&gt;
&lt;p&gt;So give clients three kinds of proof.&lt;/p&gt;
&lt;h2&gt;Proof 1: they can see it working&lt;/h2&gt;
&lt;p&gt;The strongest proof is the one they can check whenever they like.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; each client gets a portal in their colours, with their logo. On Agency and Scale it can sit on your web address or theirs, with no sign of us.&lt;/p&gt;
&lt;p&gt;They sign in with a link sent to their email. It works once and expires after 15 minutes, so there is no password to forget and no reason not to look.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g1-lead-to-portal.gif&quot; alt=&quot;A customer fills in a form, gets a text 52 seconds later, and the enquiry appears in the owner&amp;#39;s portal with &amp;quot;52 sec&amp;quot; next to it.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 2: What the owner sees: every enquiry, and how fast it was answered. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The owner is impressed by a name he recognises next to &amp;quot;52 sec&amp;quot;, a customer who did not go to a competitor.&lt;/p&gt;
&lt;h2&gt;Proof 2: a ten-second summary&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; on the first of every month, a one-page report goes to the client, and the same month stays in their portal. It has four numbers, one chart and one plain sentence, in their colours.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g4-month-report.gif&quot; alt=&quot;The monthly report shows 36 new leads, 69% replied to in under 2 minutes, a typical reply of 1 minute 4 seconds, 108 texts and emails sent, and a sentence comparing the month with the one before.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 3: Sent on the 1st. Nobody presses send. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Three rules make a report like this work, whatever tool you use:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Numbers about their customers.&lt;/strong&gt; &amp;quot;36 people got in touch&amp;quot; beats &amp;quot;214 runs&amp;quot;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A comparison.&lt;/strong&gt; A line such as &amp;quot;Response time improved 34 seconds versus August&amp;quot; tells them it is getting better.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No explaining needed.&lt;/strong&gt; If a number needs a sentence of context, leave it out.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Attach it to your invoice. The owner opens the email and sees what the month bought before he sees the price.&lt;/p&gt;
&lt;h2&gt;Proof 3: the problem they never saw&lt;/h2&gt;
&lt;p&gt;Things break. A form gets changed, a password expires, a connected app stops sending updates. Clients understand that things break, and they find it hard to forgive hearing about it before you do.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; each workflow&amp;#39;s normal rhythm is learned from its runs. If one goes quiet for three times its usual gap, it moves to &lt;strong&gt;Stopped&lt;/strong&gt; and you get an email. Your client is not told. You fix it, and Thrum tells you when it is &lt;strong&gt;Thrumming&lt;/strong&gt; (running normally) again.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g2-silence-to-alert.gif&quot; alt=&quot;A workflow goes quiet overnight and moves to Stopped. The alert email arrives saying the client has not been told. After the fix it is Thrumming again and a recovery email confirms it.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 4: You hear first. You fix it. Then you tell the client in one line. Example clients.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Then send one line, before they ask, like this one.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Your quote form stopped sending enquiries on Friday evening. I caught it on Saturday morning, fixed it, and it has run normally since.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;That message impresses clients more than any feature. It tells them someone is watching, which is exactly what the monthly fee pays for.&lt;/p&gt;
&lt;h2&gt;Make the first week feel easy&lt;/h2&gt;
&lt;p&gt;First impressions are made during setup. If the first two weeks are full of &amp;quot;can you send me your login again&amp;quot;, the client starts to doubt you.&lt;/p&gt;
&lt;p&gt;Ask for everything you need in one message, on day one. A template with a checklist makes that easy, because you know exactly which accounts and details are missing for this client.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; each client made from a template gets a list of what it still needs, and nothing goes live half-finished. When the list is done, you switch it on, and it shows &lt;strong&gt;Idle&lt;/strong&gt; until the first enquiry arrives.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g3-checklist-to-live.gif&quot; alt=&quot;A setup checklist for a client made from a template: a texting key is added, an optional step is turned off, the workflow is switched on, and it moves from Idle to Thrumming when the first enquiry comes in.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 5: A new client, set up from a template, switched on. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;The first 30 days with a new client&lt;/h2&gt;
&lt;p&gt;Most of a client&amp;#39;s opinion of you is formed in the first month. Here is a simple plan for it.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Day 1.&lt;/strong&gt; Send one message asking for everything you need. Once it is switched on, send the portal address and one line on what they will see there.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Week 1.&lt;/strong&gt; When the first enquiries arrive, send a short note: &amp;quot;Your first three enquiries all heard back in under two minutes. You can see them in your portal.&amp;quot;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Any time something breaks.&lt;/strong&gt; Fix it first, then tell them in one line what happened and that it is sorted. Do not wait for them to ask.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The 1st of the month.&lt;/strong&gt; The report goes out on its own. Send your invoice the same day, so the two arrive together.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Month 2.&lt;/strong&gt; Ask what they would fix next. A client who can see the first automation working is the easiest person to sell the second one to.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; the portal, the alerts and the report are built in for each client, so this plan comes down to four short messages from you. Everything else is shown to the client without you writing it up.&lt;/p&gt;
&lt;h2&gt;Small habits that impress&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Use their words.&lt;/strong&gt; Say &amp;quot;enquiries&amp;quot; or &amp;quot;jobs&amp;quot; if that is what they say. Keep words like &amp;quot;workflows&amp;quot; and &amp;quot;runs&amp;quot; for yourself.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Use names and numbers.&lt;/strong&gt; &amp;quot;Daniel asked about a boiler service at 9:14am and got a text two minutes later&amp;quot; beats &amp;quot;the system is working well&amp;quot;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Send the good news too.&lt;/strong&gt; A short note when something recovers, or when they had a record month.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Never send a screenshot of the tool.&lt;/strong&gt; If you have to explain it, it is evidence for you.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Say what happens next.&lt;/strong&gt; Every message ends with either an action or &amp;quot;nothing needed from you&amp;quot;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;What Thrum has not shipped yet&lt;/h2&gt;
&lt;p&gt;Forms are live today. The portal, the monthly report and the alerts are built and not yet used by any customer.&lt;/p&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Clients stay when they can see three things: the work being done, the value it created, and that you were watching.&lt;/li&gt;
&lt;li&gt;Proof of work is the portal. Proof of value is the report on the 1st. Proof you were watching is the problem you fixed before they noticed.&lt;/li&gt;
&lt;li&gt;Thrum produces all three for each client, without you writing them up by hand.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Solo is $20 a seat a month, and each seat carries one client. Every account starts with a 14-day trial for two clients, with no card.&lt;/p&gt;
</content:encoded></item><item><title>Work your client cannot see does not get renewed</title><link>https://www.thrum.run/blog/invisible-automation-work-renewal</link><guid isPermaLink="true">https://www.thrum.run/blog/invisible-automation-work-renewal</guid><pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate><description>Good automation leaves a client nothing to remember when the monthly fee comes up for review. Here is what to show them, in a portal and a monthly report.</description><content:encoded>&lt;p&gt;The best automation work is the work a client never thinks about. That is also why it is the first line they cut. We built Thrum&amp;#39;s portal and monthly report to make good automation visible to the person paying for it.&lt;/p&gt;
&lt;p&gt;This short post explains why invisible work gets cancelled, and what to show instead.&lt;/p&gt;
&lt;h2&gt;The renewal decided without you in the room&lt;/h2&gt;
&lt;p&gt;When a monthly fee comes up for review, the client weighs what they remember you doing. A workflow, a set of steps that runs by itself, that works perfectly leaves nothing to remember. The customer got a text in two minutes. The review request went out the day after the job. None of it reached the owner&amp;#39;s attention. That was the point of the work, and at review time it leaves the owner with nothing to picture.&lt;/p&gt;
&lt;p&gt;Picture a roofer going through monthly costs on a Sunday night. Every other line is something he can picture: the van, the accountant, the software. Yours is &amp;quot;the automation thing&amp;quot;. He cannot picture what it does, so it looks like the easiest saving on the page.&lt;/p&gt;
&lt;h2&gt;Evidence for you, and evidence for them&lt;/h2&gt;
&lt;p&gt;A common mistake is sending how many times the automation ran, a screenshot of the tool or a list of green ticks. That is evidence for you, and to the client it is noise.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/illustrations/i4-what-clients-see.png&quot; alt=&quot;On the left, a technical run log with codes is captioned &amp;quot;evidence for you&amp;quot;. On the right, a plain summary reading &amp;quot;36 people got in touch. 25 heard back in under 2 minutes&amp;quot; is captioned &amp;quot;evidence for them&amp;quot;.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 1: Both are true, and the plain summary on the right is what gets the monthly fee renewed.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The evidence a client notices is about their own customers, like this example.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;Daniel asked about a boiler service at 9:14am. He got a text back two minutes later.&amp;quot;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;No technical words, no codes, no mention of any software. Thirty of those in a month is proof that the line on the budget is doing something.&lt;/p&gt;
&lt;p&gt;Leave out anything the client would need you to explain, such as percentages of time it was working, how many times it ran or the name of the tool behind it. If a number needs a sentence of context before it means something to a plumber, keep it on your own screen.&lt;/p&gt;
&lt;h2&gt;Where Thrum puts it&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; each client gets a portal on their phone, in their colours. It shows who got in touch, what happened next, and how fast they heard back. On Agency and Scale it can sit on your web address or theirs. They sign in with a link that works once and expires after 15 minutes, so there is no password to forget.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g1-lead-to-portal.gif&quot; alt=&quot;A customer fills in a quote form, gets a text back 52 seconds later, and the enquiry appears in the owner&amp;#39;s portal with its response time.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 2: What the owner sees, seconds after a customer asks. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;On the first of each month, Thrum sends a one-page report with four numbers, one chart and one plain sentence, in the client&amp;#39;s colours and under their name. You attach it to the invoice, and the invoice stops being the only thing they hear from you.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g4-month-report.gif&quot; alt=&quot;The monthly report shows 36 new leads, 69% replied to in under 2 minutes, a typical reply of 1 minute 4 seconds, and 108 texts and emails sent automatically.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 3: The month in plain numbers. &amp;quot;Sent automatically&amp;quot; answers &amp;quot;what am I paying for&amp;quot;. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Do this even without Thrum&lt;/h2&gt;
&lt;p&gt;Start with the report. On the first of next month, send each client four numbers about their business that your work produced: enquiries handled, how fast they were answered, reminders sent, reviews requested. One paragraph. No screenshots. If a number went the wrong way, say so and say what you changed. A client who hears the bad month from you first trusts the good months more.&lt;/p&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Clients renew what they remember, and good automation leaves nothing to remember.&lt;/li&gt;
&lt;li&gt;Show evidence about their customers, in words they use.&lt;/li&gt;
&lt;li&gt;Thrum gives every client a portal and a report on the 1st, so the work is visible without you writing it up.&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>How to make money selling automation to small businesses</title><link>https://www.thrum.run/blog/make-money-selling-automation</link><guid isPermaLink="true">https://www.thrum.run/blog/make-money-selling-automation</guid><pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate><description>What to sell to small businesses, who to sell it to, how to set a setup fee and a monthly fee, and how to keep clients paying for your automation work.</description><content:encoded>&lt;p&gt;Small businesses pay for fewer lost customers, and automation is one way to give them that. We make Thrum, the software that runs this work for each client, so its screens appear below. If you sell that, charge a one-off setup fee plus a monthly fee, and show the owner every month that it worked, you have a business that grows one client at a time.&lt;/p&gt;
&lt;p&gt;This guide covers what to sell, who to sell it to, how to price it, and how to keep clients paying. The numbers are examples. Put in your own.&lt;/p&gt;
&lt;h2&gt;Sell one problem that costs money each week&lt;/h2&gt;
&lt;p&gt;Most freelancers open with a menu: &amp;quot;I can automate your emails, your customer records, your invoices.&amp;quot; A menu gives a plumber nothing to picture. What he remembers is that last Tuesday a customer filled in his website form, nobody answered for six hours, and the job went to someone else.&lt;/p&gt;
&lt;p&gt;Sell the fix for that one problem. These two come up most.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Slow replies to new enquiries.&lt;/strong&gt; A well-known 2011 Harvard Business Review study timed how fast 2,241 US companies answered a web enquiry. A companion analysis of 1.25 million enquiries at 42 companies found that firms that tried to reach someone within an hour were nearly seven times as likely to have a real conversation with a decision-maker as firms that tried even an hour later. The data is old, and owners say the same today, that people ask several businesses and often go with whoever answers first.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Missed phone calls.&lt;/strong&gt; Call-tracking company Invoca&amp;#39;s 2026 home-services report, drawn from more than 70 million calls across ten industries, found that only 52% of callers to home-service businesses spoke to a person. Invoca sells call tools, so treat the figure as a rough guide. Any owner will tell you the same thing in plainer words: &amp;quot;We miss calls when we are on a job.&amp;quot;&lt;/p&gt;
&lt;p&gt;The animation below shows the fix for slow replies as it runs.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g1-lead-to-portal.gif&quot; alt=&quot;A customer fills in a quote form, gets a text back 52 seconds later, and the enquiry appears in the owner&amp;#39;s portal with its response time.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;From the form to the owner&amp;#39;s phone in Thrum, with nobody touching it. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A customer asks, and seconds later they hear back. The owner sees it on his phone. That is something he will pay for, because he can picture the jobs it saves.&lt;/p&gt;
&lt;h2&gt;Who to sell it to&lt;/h2&gt;
&lt;p&gt;The best clients have three things in common.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;One customer is worth a lot.&lt;/strong&gt; A boiler repair, a dental implant, a roof survey. If one extra job a month covers your fee, the sale is easy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Enquiries come in by form or phone.&lt;/strong&gt; That is where the delay happens, and where automation helps.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The owner is too busy to answer fast.&lt;/strong&gt; They are on a roof, under a sink, or with a patient.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Trades, clinics, salons, vets and letting agents fit. Shops that sell online mostly do not, because their checkout already does the work.&lt;/p&gt;
&lt;p&gt;Before you pitch, ask one question: &amp;quot;What is one new customer worth to you?&amp;quot; If the answer is $400 and your fix saves two customers a month, that is $800 a month of value, and your price has something to stand on.&lt;/p&gt;
&lt;h2&gt;Charge a setup fee and a monthly fee&lt;/h2&gt;
&lt;p&gt;Charge two things.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A setup fee, paid once.&lt;/strong&gt; This pays for building, testing and switching it on. Upwork&amp;#39;s hiring guide for automation freelancers puts a single automated workflow at roughly $300 to $800 and a multi-step one at $800 to $3,000. Agency guides say fees for basic automations often start at $1,000 to $2,500. None of these figures comes from a proper survey. They are what people report, so use them as a sanity check.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A monthly fee.&lt;/strong&gt; This pays for keeping it running, fixing it when something changes, and showing the results. It is the part that turns a project into a business.&lt;/p&gt;
&lt;p&gt;Here is what three clients look like with an example setup fee of $1,500 and a monthly fee of $300.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/illustrations/i2-money-math.png&quot; alt=&quot;A chart shows one client bringing a $1,500 setup fee and a $300 monthly fee, Solo at $20 a seat for that client, and three clients signed in months 1 to 3 bringing $14,400 in the first year and $900 a month from month 4.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Illustrative numbers. The shape matters more than the totals.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Three clients bring in $14,400 in the first year and $900 every month after the third. On Thrum, Solo costs $20 a seat a month and each seat carries one client, so three clients cost $60 a month.&lt;/p&gt;
&lt;p&gt;From month 4 onwards, all of the money comes from the monthly fee. That fee is the business, and it is also the first thing a client cancels when they cannot see what it pays for.&lt;/p&gt;
&lt;h2&gt;Make the monthly fee an easy yes&lt;/h2&gt;
&lt;p&gt;The usual reason a client cancels the monthly fee is that they forget what it does. When an automation works well, nothing happens that the owner notices. The customer got a text, the job got booked, and the owner never thought about it.&lt;/p&gt;
&lt;p&gt;So the monthly fee has to come with three kinds of evidence.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;They can see it working.&lt;/strong&gt; Every enquiry, and how fast it was answered, on their phone, in their own colours.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;They hear about problems from you first.&lt;/strong&gt; If something stops, you know before they do, you fix it, and you tell them in one line.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;They get a summary every month.&lt;/strong&gt; Four numbers and one plain sentence they can read in ten seconds.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Thrum does all three. Each client gets a portal in their own colours and logo, and on Agency and Scale it can sit on your web address or theirs, with no sign of us. On the first of each month, a one-page report goes to the client.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g4-month-report.gif&quot; alt=&quot;The monthly report for an example business counts up to 36 new leads, 69% replied to in under 2 minutes, a typical reply of 1 minute 4 seconds, and 108 texts and emails sent.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The month on one page. Thrum sends it to the client, and your copy goes with your invoice.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;When the invoice and the report arrive together, the owner sees 36 customers who heard back in about a minute right next to the bill.&lt;/p&gt;
&lt;h2&gt;Set up each new client in hours&lt;/h2&gt;
&lt;p&gt;Your second client should not take as long as your first. If it does, your profit goes on setup.&lt;/p&gt;
&lt;p&gt;Build the automation once, then turn it into a template with the few details that change per client: the business name, the owner&amp;#39;s mobile, the words that mean &amp;quot;urgent&amp;quot;, a booking link. For each new client, Thrum lists what is still missing, and nothing runs until the list is done.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g3-checklist-to-live.gif&quot; alt=&quot;A setup checklist fills in as a texting key is added, an optional step is turned off and the workflow is switched on, and it moves from Idle to Thrumming when the first lead comes in.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;A new client from a template: fill the gaps, switch it on.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In Thrum, the client&amp;#39;s texting account details go in, the steps they do not need get turned off, and it goes live. Idle means it is waiting for the first enquiry. Thrumming means it is running normally.&lt;/p&gt;
&lt;h2&gt;The texting rule most freelancers learn too late&lt;/h2&gt;
&lt;p&gt;If your clients are in the US and your automation sends texts from a normal local phone number, the number has to be registered first. This is called A2P 10DLC registration. Since September 2023, Twilio blocks texts from unregistered local numbers to US phones.&lt;/p&gt;
&lt;p&gt;Registration covers the business (the brand) and what it sends (the campaign). Twilio says campaign checks take about 7 business days, and up to 10 when it is busy. Build that into your timeline, or your first week looks broken when it is not.&lt;/p&gt;
&lt;p&gt;Two more rules apply.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Opt-outs.&lt;/strong&gt; People must be able to reply STOP and stop getting texts. Twilio handles STOP and similar words by default.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consent.&lt;/strong&gt; Only text people who asked to be contacted, for example by filling in the form. Marketing texts need stronger written consent.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;None of this is legal advice. It tells you what to ask, so you sound like you know what you are doing when the owner asks you.&lt;/p&gt;
&lt;h2&gt;Your first 30 days&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Pick one problem.&lt;/strong&gt; Slow replies or missed calls.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Pick one kind of business.&lt;/strong&gt; Plumbers, dentists or salons. One kind, so your examples fit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Build it once, properly.&lt;/strong&gt; Test it with a friend&amp;#39;s phone. Make it a template.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Talk to ten owners.&lt;/strong&gt; Ask what one new customer is worth, and how fast they reply now.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Offer the first one at a fair price&lt;/strong&gt; in exchange for frank feedback and permission to describe the results.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Show the results.&lt;/strong&gt; In Thrum, the portal is there from the day you add the client, and the report goes out on the first of the month.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ask for the next problem.&lt;/strong&gt; A client who can see the first fix working is the easiest person to sell the second one to.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Every Thrum account starts with a 14-day trial for two clients, with no card, so your first build costs nothing but your time. After that, Solo is $20 a seat a month, one client a seat.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Oldroyd, McElheran and Elkington, &amp;quot;The Short Life of Online Sales Leads&amp;quot;, Harvard Business Review, March 2011, including the companion analysis of 1.25 million leads at 42 companies: &lt;a href=&quot;https://hbr.org/2011/03/the-short-life-of-online-sales-leads&quot;&gt;https://hbr.org/2011/03/the-short-life-of-online-sales-leads&lt;/a&gt; (figures as quoted in &lt;a href=&quot;https://customerthink.com/how_fast_are_you/&quot;&gt;https://customerthink.com/how_fast_are_you/&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Invoca, Home Services Lead Conversion Benchmarks Report 2026 (vendor): &lt;a href=&quot;https://invoca.com/reports/the-invoca-home-services-lead-conversion-benchmarks-report-2026&quot;&gt;https://invoca.com/reports/the-invoca-home-services-lead-conversion-benchmarks-report-2026&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Upwork, hire Zapier developers (rate and project guidance): &lt;a href=&quot;https://www.upwork.com/hire/zapier-developers/&quot;&gt;https://www.upwork.com/hire/zapier-developers/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Digital Agency Network, AI automation pricing (anecdotal): &lt;a href=&quot;https://digitalagencynetwork.com/ai-automation-pricing/&quot;&gt;https://digitalagencynetwork.com/ai-automation-pricing/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Twilio, A2P 10DLC: &lt;a href=&quot;https://www.twilio.com/docs/messaging/compliance/a2p-10dlc&quot;&gt;https://www.twilio.com/docs/messaging/compliance/a2p-10dlc&lt;/a&gt; and &lt;a href=&quot;https://support.twilio.com/hc/en-us/articles/1260800720410-What-is-A2P-10DLC&quot;&gt;https://support.twilio.com/hc/en-us/articles/1260800720410-What-is-A2P-10DLC&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Twilio, full blocking of unregistered traffic: &lt;a href=&quot;https://www.twilio.com/en-us/changelog/-u-s--a2p-10dlc--full-blocking-of-traffic-sent-from-unregistered&quot;&gt;https://www.twilio.com/en-us/changelog/-u-s--a2p-10dlc--full-blocking-of-traffic-sent-from-unregistered&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Twilio, opt-out keywords: &lt;a href=&quot;https://www.twilio.com/en-us/blog/insights/best-practices/update-to-fcc-s-sms-opt-out-keywords&quot;&gt;https://www.twilio.com/en-us/blog/insights/best-practices/update-to-fcc-s-sms-opt-out-keywords&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;47 CFR 64.1200 (TCPA rules): &lt;a href=&quot;https://www.ecfr.gov/current/title-47/section-64.1200&quot;&gt;https://www.ecfr.gov/current/title-47/section-64.1200&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>You lose the client when they notice first</title><link>https://www.thrum.run/blog/retainer-dies-when-client-notices-first</link><guid isPermaLink="true">https://www.thrum.run/blog/retainer-dies-when-client-notices-first</guid><pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate><description>Why the order of events decides whether a client stays after an automation breaks, why silent failures matter most, and how to hear about them before they do.</description><content:encoded>&lt;p&gt;We built Thrum around one observation about automation work for small businesses. The client you lose is the one who finds out about a broken automation before you do.&lt;/p&gt;
&lt;p&gt;Things break in every business, and owners know it. What they find hard to forgive is learning that the person they pay every month to watch it was not watching. This post explains why the order of events matters more than the failure, why the failures that matter most never show an error, and how Thrum makes sure you are the first to know.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g2-silence-to-alert.gif&quot; alt=&quot;Example clients sit on one screen. A workflow goes quiet overnight, moves to Stopped and rises to the top of the list, the alert email arrives, and after the fix it is Thrumming again with a recovery email.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 1: In Thrum, a client&amp;#39;s workflow goes quiet overnight. You get the alert, you fix it, and you hear when it is running again. Example clients.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;The same weekend, twice&lt;/h2&gt;
&lt;p&gt;Take an example client, Northside Plumbing. You built them a workflow, a set of steps that runs by itself, called Lead Rescue. When someone fills in the quote form on their website, the customer gets a text back within about a minute (or at 08:00, if they ask overnight) and the owner gets the details on his phone. On a normal week it runs about six times a day. The business, the times and the details here are illustrative.&lt;/p&gt;
&lt;p&gt;On Friday at 6:40pm the form stops sending enquiries to the workflow. Maybe someone changed the website and the form came off the page. Maybe a password the automation uses was changed. Whatever the cause, nothing shows an error. No run starts, so no run fails.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Version one.&lt;/strong&gt; Monday, 9:05am, the owner calls. Two customers told his office manager that nobody got back to them about a quote, and one booked someone else. You check the history and see it last ran on Friday evening. You fix it in fifteen minutes, then spend the rest of the call explaining why the thing he pays you to keep running was off for two and a half days, and why you did not know.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Version two.&lt;/strong&gt; On Saturday at 8:40am, the alert below arrives in your inbox from Thrum.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/shots/s7-alert-body.png&quot; alt=&quot;The alert email says that Lead Rescue for Northside Plumbing has not run for 14 hours, that it usually runs every 4 hours so the alert comes after 12 hours of silence, and that your client has not been told.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 2: The alert as Thrum renders it. It goes to you, never to your client.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;You fix it before breakfast and Lead Rescue goes back to Thrumming (running normally). On Monday you mention it in one line: &amp;quot;Your quote form stopped sending enquiries on Friday evening. I caught it on Saturday morning and it has run normally since.&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/diagrams/d4-two-weekends.png&quot; alt=&quot;Two timelines show the same weekend. With nobody watching, the workflow is Stopped for 62 hours until the owner calls on Monday. With Thrum watching, the alert arrives on Saturday morning and the workflow is Thrumming again by 08:55.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 3: The same failure and the same fifteen-minute fix, in a different order of events. Illustrative times.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Why the order matters more than the failure&lt;/h2&gt;
&lt;p&gt;Your clients run businesses where things go wrong each week. The van fails its test, the card machine drops out, a supplier sends the wrong part. They do not expect software to be perfect.&lt;/p&gt;
&lt;p&gt;What turns a problem into a lost client is finding out that nobody was watching. When the client spots it first, the question in their head becomes &amp;quot;what else has been off that I do not know about&amp;quot;.&lt;/p&gt;
&lt;p&gt;A monthly fee is a bet, renewed every month, that you are paying attention when the client is not. Each time they catch a problem before you, the bet looks worse. The cancellation tends to come later, at the next price review, when a cheaper offer arrives, or when they decide to &amp;quot;handle it ourselves for a bit&amp;quot;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; this is why the alert goes only to you. Your client is never told about a problem you have not had the chance to fix.&lt;/p&gt;
&lt;h2&gt;The failures that matter show no error&lt;/h2&gt;
&lt;p&gt;Most monitoring is built around errors, so a failed step sends you an email. That covers the runs that happen and go wrong. Many of the failures that lose clients are runs that never start, and here are four common ones.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The automation gets paused during a test and never switched back on.&lt;/li&gt;
&lt;li&gt;A password or access key expires, and the connected app stops sending updates.&lt;/li&gt;
&lt;li&gt;Someone on the client&amp;#39;s side takes the form off the website.&lt;/li&gt;
&lt;li&gt;They move to a new booking system, and the link that fed the automation is gone.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In each case the error count is zero. Your inbox is quiet, and a quiet inbox looks like good news. From the outside, silence and a working system look the same, unless something knows what normal looks like.&lt;/p&gt;
&lt;h2&gt;How Thrum watches for silence&lt;/h2&gt;
&lt;p&gt;Thrum runs the workflows you build for your clients and records each run. From those runs it learns each workflow&amp;#39;s rhythm, meaning how often it runs, how long it takes and how often it fails. After 10 runs it knows what normal looks like.&lt;/p&gt;
&lt;p&gt;Then it watches for the gap. Silence for three times the usual gap moves a workflow to &lt;strong&gt;Stopped&lt;/strong&gt;, and you get an email. A workflow with a usual four-hour gap goes Stopped after twelve quiet hours. For a monthly invoice chase, three quiet days is normal, and it stays &lt;strong&gt;Thrumming&lt;/strong&gt;. The alert is never sooner than 6 hours and never later than 7 days. If you know better than the history, you can tell Thrum directly how often a workflow should run.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/diagrams/d3-silence-threshold.png&quot; alt=&quot;Two timelines compare two workflows. One that runs every 4 hours goes Stopped after 12 quiet hours. A monthly workflow stays Thrumming through three quiet days and goes Stopped at the 7-day cap.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 4: Thrum times the alert against each workflow&amp;#39;s own rhythm, never sooner than 6 hours and never later than 7 days of silence.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Thrum also catches the slower kind of trouble. Three failed runs in a row, a fifth of recent runs failing, or runs taking three times longer than usual moves a workflow to &lt;strong&gt;Degraded&lt;/strong&gt; (still running, worth a look today). A workflow with nothing to do yet is &lt;strong&gt;Idle&lt;/strong&gt;, which is not a problem.&lt;/p&gt;
&lt;p&gt;If a workflow stays Stopped, you get a reminder once a day. When it recovers, you hear that too, so you know the fix held. On your screen, all your clients sit on one list with anything Stopped at the top, so anything red you see there in the morning is what needs you that day.&lt;/p&gt;
&lt;h2&gt;Make the good weeks visible too&lt;/h2&gt;
&lt;p&gt;Hearing first is half of it. The other half is showing the work when nothing is wrong, so the client&amp;#39;s picture of you is not built from the one weekend something broke.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In Thrum:&lt;/strong&gt; each client gets a portal in their own colours, with their logo. It shows who got in touch, what happened next and how fast they heard back, with no technical words. On Agency and Scale it can sit on your web address or theirs, and our name appears nowhere in it. On the first of each month, a one-page report goes to the client.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g4-month-report.gif&quot; alt=&quot;The monthly report for an example business counts up to 36 new leads, 69% replied to in under 2 minutes, a typical reply of 1 minute 4 seconds, and 108 texts and emails sent.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 5: The month on one page, sent on the 1st. Thrum sends it to the client, and your copy goes with your invoice. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;The arithmetic&lt;/h2&gt;
&lt;p&gt;These numbers are illustrative, so swap in your own. Say you look after three clients at $400 a month each. That is $1,200 a month. Lose one of them to a weekend like version one and you lose $4,800 over the next year, before counting the referral they will not give you.&lt;/p&gt;
&lt;p&gt;In Thrum, Solo is $20 a seat a month, and each seat carries one client, so those three clients cost $60 a month. Every account starts with a 14-day trial for two clients, with no card.&lt;/p&gt;
&lt;h2&gt;This week&amp;#39;s steps, with or without Thrum&lt;/h2&gt;
&lt;p&gt;You can start hearing first today with a list and a habit.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;List each workflow you run for a client.&lt;/strong&gt; One line each: client, workflow, what starts it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Write down its normal rhythm.&lt;/strong&gt; Every few hours, daily, weekly. If you do not know, look at the last 30 days.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Set a silence limit&lt;/strong&gt; of roughly three times the normal gap.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Check the last run against that limit each morning,&lt;/strong&gt; before email.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Decide what you tell the client, and when.&lt;/strong&gt; One plain sentence, after it is fixed, before they ask.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Do that for a month and you will know how often your clients&amp;#39; workflows go quiet, and how much of your morning it costs to check by hand. If the second number is bigger than you like, that is the part Thrum does for you.&lt;/p&gt;
&lt;h2&gt;What Thrum has not shipped yet&lt;/h2&gt;
&lt;p&gt;Forms are live today. The portal, the monthly report and the alerts are built and not yet used by any customer. Thrum runs the workflows itself, so it cannot watch automations you already built in Zapier or n8n.&lt;/p&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The client you lose is the one who notices a problem before you do.&lt;/li&gt;
&lt;li&gt;The failures that matter most are silent, with no run and so no error.&lt;/li&gt;
&lt;li&gt;Thrum learns each workflow&amp;#39;s rhythm and alerts you, never the client, when it goes quiet or starts failing.&lt;/li&gt;
&lt;li&gt;The portal and the monthly report make the good weeks visible, so one bad weekend does not define you.&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item><item><title>From signed proposal to paid invoice: how Thrum runs the whole loop</title><link>https://www.thrum.run/blog/signed-proposal-to-paid-invoice</link><guid isPermaLink="true">https://www.thrum.run/blog/signed-proposal-to-paid-invoice</guid><pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate><description>One client relationship in Thrum, stage by stage: the signed proposal, the automatic setup, the workflow, the portal, the alerts, the report and the invoice.</description><content:encoded>&lt;p&gt;Thrum is a client delivery platform for people who sell automation to small businesses. We designed it so that the whole relationship with a client lives in one place and runs by itself, from the proposal they sign to the invoice they pay. A person steps in at four moments, for decisions and fixes.&lt;/p&gt;
&lt;p&gt;This post walks through that loop stage by stage, with the screens. It also says plainly what is live today, what is built, and what is built but has not yet run with a real client.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g5-signal-flow.gif&quot; alt=&quot;An animated diagram inside a Thrum frame shows a customer typing into a quote form and pressing send. A green line travels into the workflow, where each step turns green with its time, the urgent branch is taken and the other branch dims. The line then runs into the owner&amp;#39;s portal, where the enquiry appears with a response time of 52 seconds.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 1: One enquiry, start to finish. The form, the workflow and the owner&amp;#39;s portal all run in Thrum. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;The four moments a person steps in&lt;/h2&gt;
&lt;p&gt;Even a fully automated loop needs people for decisions and fixes, while the copying of details between screens runs by itself. In Thrum, you step in four times.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;You write the proposal and send the link.&lt;/strong&gt; The scope and the price are yours.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You add the client&amp;#39;s account details and switch the workflows on.&lt;/strong&gt; A workflow is a set of steps that runs by itself. The details are things like their texting account and their email sender.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You tell the client where their portal is.&lt;/strong&gt; One web address. They sign in with a link sent to their email.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You answer the alert.&lt;/strong&gt; When something goes quiet, a person fixes it. Thrum makes sure that person is you, and that you hear first.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Everything between those four runs by itself, month after month.&lt;/p&gt;
&lt;h2&gt;Stage 1: the proposal is signed&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Status: built, not yet run with a client.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;You write the proposal in Thrum and send the client a link. They read it without making an account. To accept, they enter a six-digit code sent to the email address you sent it to.&lt;/p&gt;
&lt;p&gt;Thrum keeps a record of who signed and when, the exact text they saw, and the agreement PDF itself. If you edit a sent proposal, the old link stops working and the proposal goes back to draft, so the new version goes out under a new link. Nobody ever signs terms that changed under them. A proposal stays open for 30 days unless you choose otherwise.&lt;/p&gt;
&lt;h2&gt;Stage 2: the client&amp;#39;s side sets itself up&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Status: built, not yet run with a client.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The moment the client accepts, Thrum creates their side in one step.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;their workspace, at the portal address the proposal reserved&lt;/li&gt;
&lt;li&gt;the forms and workflows you chose for this kind of client, switched off&lt;/li&gt;
&lt;li&gt;a request for each account the client has to supply&lt;/li&gt;
&lt;li&gt;a portal sign-in for their email&lt;/li&gt;
&lt;li&gt;the signed agreement, filed in their workspace&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If your plan is full when they sign, their signature still stands. The proposal waits as &amp;quot;signed, not set up&amp;quot; and finishes setting up once there is room. The client never sees your billing.&lt;/p&gt;
&lt;h2&gt;Stage 3: account details in, switched on&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Status: built. This is your second moment.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Nothing runs until it has what it needs. For each client, Thrum lists what is missing. Usually that is the key to their texting account and, if they have one, a link to their customer list or spreadsheet.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g3-checklist-to-live.gif&quot; alt=&quot;A setup checklist fills in as a texting key is added, an optional step is turned off and the workflow is switched on, and it moves from Idle to Thrumming when the first enquiry comes in.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 2: A new client made from a template. Fill the gaps, switch it on. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This is deliberate. A half-set-up workflow that texts a real customer is worse than one that never runs. When the list is done, you press Publish and Switch On. The workflow shows &lt;strong&gt;Idle&lt;/strong&gt; (nothing has come in yet) until the first enquiry arrives, then &lt;strong&gt;Thrumming&lt;/strong&gt; (running normally).&lt;/p&gt;
&lt;h2&gt;Stage 4: a customer fills in the form&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Status: live.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The client&amp;#39;s customer fills in a form on the business&amp;#39;s website, such as a quote request, a booking or a call-out. Forms can sit inside the page, open from a button, or take a whole page. However the questions are worded, the workflow picks out the same four things, which are the customer&amp;#39;s name, email, phone and what they need.&lt;/p&gt;
&lt;p&gt;Forms are the part of Thrum that is live today.&lt;/p&gt;
&lt;h2&gt;Stage 5: Lead Rescue runs&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Status: built.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The form starts the workflow. Lead Rescue is the ready-made template most people start from, and it shows what &amp;quot;runs by itself&amp;quot; means in practice.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g6-canvas-run.gif&quot; alt=&quot;Thrum&amp;#39;s canvas shows Lead Rescue as one run moves through it. The form arriving, the instant reply and the email acknowledgement turn green, the Emergency? check takes the urgent branch, the owner is texted, and after the wait the owner has marked it contacted, while the other branch is skipped. A panel lists each step in plain words with its time.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 3: One run moving through Lead Rescue in Thrum&amp;#39;s canvas. Simplified illustration using the template&amp;#39;s wording for each step.&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The customer gets a text within about a minute, and an email if they gave one. Texts wait out the night, so an enquiry that arrives between 21:00 and 08:00 is answered at 08:00.&lt;/li&gt;
&lt;li&gt;The details are copied to the client&amp;#39;s customer list or spreadsheet, if they have one.&lt;/li&gt;
&lt;li&gt;If the message uses one of the client&amp;#39;s urgent words (leak, burst, no heat), the owner gets a text with the details. If nobody marks the enquiry contacted within 10 minutes, the text goes to a backup number, if you set one.&lt;/li&gt;
&lt;li&gt;Otherwise, Thrum waits an hour. If nobody has been in touch by then, the customer gets a text with a link to book, and the owner gets one line by email for each enquiry that was rescued.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Five details make it one client&amp;#39;s: business name, owner&amp;#39;s mobile, owner&amp;#39;s email, urgent words and booking link. The checks look at the latest state. If the owner marks an enquiry contacted from his phone during a wait, the run sees it and stops, so nobody gets texted twice.&lt;/p&gt;
&lt;h2&gt;Stage 6: the client sees it&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Status: built. This is your third moment.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In Thrum, your client gets a portal in their own colours, with their logo, so they never have to open an automation tool. On Agency and Scale it can sit on your web address or theirs, and our name appears nowhere in it.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/shots/s3-portal-leads.png&quot; alt=&quot;The portal&amp;#39;s leads screen for an example plumber, in their violet, lists each enquiry, when it came in, and how fast the customer heard back.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 4: The portal on a phone, in an example client&amp;#39;s colours. Real product screen.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;It opens on two screens, who got in touch and how the month went, and shows only what the client has, so a client with bookings or an inbox sees those too. No technical words, no codes. To the owner it reads as a list of their customers and how quickly each one heard back.&lt;/p&gt;
&lt;h2&gt;Health watches stages 4 to 8 throughout&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Status: built. This is your fourth moment.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In Thrum, health runs alongside each stage. All your clients&amp;#39; workflows sit on one screen, with anything &lt;strong&gt;Stopped&lt;/strong&gt; at the top.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g2-silence-to-alert.gif&quot; alt=&quot;Example clients sit on one screen. A workflow goes quiet overnight, moves to Stopped and rises to the top, the alert email arrives, and after the fix it is Thrumming again.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 5: When a client&amp;#39;s workflow goes quiet, it rises to the top and the alert comes to you. Example clients.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Thrum records each run and learns each workflow&amp;#39;s rhythm. After 10 runs it knows what normal looks like. Silence for three times the usual gap moves a workflow to Stopped and sends you an email, never sooner than 6 hours and never later than 7 days. Three failures in a row, a fifth of recent runs failing, or runs three times slower than usual moves it to &lt;strong&gt;Degraded&lt;/strong&gt;. You get a reminder once a day while it stays Stopped, and a note when it recovers.&lt;/p&gt;
&lt;h2&gt;Stage 7: the report on the 1st&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Status: built.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;On the first of every month, Thrum sends each client a one-page report in their colours, with four numbers, one chart and one plain sentence. The same month stays in their portal. You get a copy, with one extra line naming any workflow that stopped, had failing runs or ran slowly that month.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g4-month-report.gif&quot; alt=&quot;The monthly report for an example business shows 36 new leads, 69% replied to in under 2 minutes, a typical reply of 1 minute 4 seconds, and 108 texts and emails sent.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 6: The month on one page. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Nobody presses send. If email is not set up yet, nothing is marked as sent, so a re-run after the fix delivers it. Either way, a client never gets the same month twice.&lt;/p&gt;
&lt;h2&gt;Stage 8: the invoice goes out&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Status: in beta, built and not yet run with a client.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Thrum records every text and email a client&amp;#39;s workflows send, with its cost and your price. When the month closes, it makes one invoice per client from those lines and sends it from your own Stripe account. A line reads like &amp;quot;Text messages, September 2026: 60 sent at $0.04 each&amp;quot; (example figures). The client gets Stripe&amp;#39;s usual email, and a View and pay link appears on that month&amp;#39;s page in their portal.&lt;/p&gt;
&lt;p&gt;Four things to know before you rely on it.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;It bills usage only.&lt;/strong&gt; Your own monthly fee is still invoiced the way you invoice it today.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No client money passes through us, and we take no cut.&lt;/strong&gt; It is your Stripe account and your key.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;It never bills twice.&lt;/strong&gt; Each client can be invoiced once per month. If Stripe refuses your key, nothing is sent, you get one email saying what to check, and that client&amp;#39;s row on your clients screen shows the problem until an invoice gets through.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Months under 50 cents are carried into the next one,&lt;/strong&gt; never dropped.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Then the month turns, and the loop from stage 4 runs again by itself.&lt;/p&gt;
&lt;h2&gt;What Thrum has not shipped yet&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A fixed-fee line on the invoice. Client invoicing bills texts and emails only.&lt;/li&gt;
&lt;li&gt;Watching automations you already built elsewhere. Thrum runs its own workflows.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;One place holds the whole client relationship, from the signed proposal to the paid invoice.&lt;/li&gt;
&lt;li&gt;You step in four times: the proposal, the account details, the portal address, and the alert.&lt;/li&gt;
&lt;li&gt;Forms are live. Workflows, health, the portal and the report are built. Proposals, setup and invoicing are built and not yet run with a client.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Solo is $20 a seat a month, and each seat carries one client. Every account starts with a 14-day trial for two clients, with no card.&lt;/p&gt;
</content:encoded></item><item><title>5 n8n alternatives that beat it (each at one job)</title><link>https://www.thrum.run/blog/tools-that-beat-n8n</link><guid isPermaLink="true">https://www.thrum.run/blog/tools-that-beat-n8n</guid><pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate><description>Thrum, Zapier, Make, Activepieces and GoHighLevel each beat n8n at one job. What each is best at, what it costs by its own pages, and where each falls short.</description><content:encoded>&lt;p&gt;We make Thrum, one of the five tools in this comparison, so read it with that in mind. We have tried to be fair. Every price and fact about another tool below comes from that tool&amp;#39;s site, checked on 15 November 2026, and each tool&amp;#39;s weak spots are listed, including ours.&lt;/p&gt;
&lt;p&gt;n8n is excellent. It charges by the full run of a workflow (a set of steps that runs by itself), and you can run it on a server you control. But no tool is best at everything. For five specific jobs, five other tools beat it. Thrum is the one built for running automations for clients and showing those clients it works.&lt;/p&gt;
&lt;h2&gt;First, what n8n is great at&lt;/h2&gt;
&lt;p&gt;n8n&amp;#39;s cloud plans charge per full run of a workflow, however many steps it has, and its pricing page says you pay only when a workflow runs from start to finish. Starter is €20 a month, billed yearly, for 2,500 runs. All plans include unlimited users, unlimited workflows and all the apps n8n connects to. A version you host yourself, the Community Edition, is available on GitHub. Its plans include AI agents, and a person can be asked to approve an agent&amp;#39;s action in another app before it happens.&lt;/p&gt;
&lt;p&gt;Its plans have nothing for handing work to clients. The pricing page is about building and running workflows, and none of its plans lists a client portal or a report you can send a client.&lt;/p&gt;
&lt;p&gt;That is fine for many jobs. For these five, there is a better choice.&lt;/p&gt;
&lt;h2&gt;1. Thrum: best for running and showing client automations&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;The job:&lt;/strong&gt; you build automations for local businesses, and each client needs to see, every month, that the work is being done.&lt;/p&gt;
&lt;p&gt;In Thrum, each workflow belongs to a client, and three things come with each client:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A portal&lt;/strong&gt; in the client&amp;#39;s colours and logo. It shows each enquiry and how fast it was answered. On Agency and Scale, it carries no platform name and can sit on the client&amp;#39;s own web address. On Solo, its footer carries a &amp;quot;Powered by Thrum&amp;quot; link and the address is ours.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A report on the first of the month&lt;/strong&gt;: four numbers, one chart, one plain sentence. Thrum sends it to the client, and your copy goes with your invoice.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An alert to you, and only you,&lt;/strong&gt; when a workflow goes quiet. Thrum learns how often each one normally runs. Three times the usual gap with nothing happening means &lt;strong&gt;Stopped&lt;/strong&gt;, and you get an email. Your client is not told.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&quot;../images/gifs/g5-signal-flow.gif&quot; alt=&quot;An animated diagram inside a Thrum frame: a quote form is sent, a green line runs through the workflow steps, one branch is taken and the other dims, and the enquiry lands in the owner&amp;#39;s portal with a 52-second response time.&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 1: The form, the workflow and the owner&amp;#39;s portal, all in Thrum. Example business.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Price:&lt;/strong&gt; Solo is $20 a seat a month, and each seat carries one client. Agency is $99 a seat a month, with 15 clients a seat, and Scale is $249 a seat a month with no client limit. Every account starts with a 14-day trial for two clients, with no card. Seats set how many clients and workflow runs you carry, and the number of steps in a workflow is not counted.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Where it falls short:&lt;/strong&gt; Thrum runs its own workflows. It does not watch the ones you already have in n8n or Zapier, though it can import your n8n workflows. It connects to fewer apps than Zapier, because it focuses on what local businesses use: texts, email, customer lists, booking and payments. You cannot host it yourself. Forms are live today. The portal, the monthly report and the alerts are built and not yet used by any customer.&lt;/p&gt;
&lt;h2&gt;2. Zapier: best for connecting almost any app, quickly&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;The job:&lt;/strong&gt; a client uses an unusual app, and you need it connected today.&lt;/p&gt;
&lt;p&gt;Zapier says it connects to more than 9,000 apps, and that this is more than any other automation tool. It also has AI agents (on separate plans), Tables for storing data, and Forms.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Price:&lt;/strong&gt; the Free plan covers 100 tasks a month. Professional starts from $19.99 a month on yearly billing. A task is each action step that runs successfully. The step that starts a workflow does not count, and neither do built-in steps such as Filter, Formatter, Paths and Delay.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Where it falls short:&lt;/strong&gt; costs rise with every step, so a busy client can get expensive. Past the plan&amp;#39;s task limit, Zapier moves you to pay-per-task billing at a higher rate per task, and if you turn that off, your workflows pause until the next usage period starts. Professional is for one person, and the Team plan, for up to 25 users, starts from $69 a month. Zapier Forms can take custom colours and drop the Zapier logo. None of the plans lists a client portal or a monthly report for a client.&lt;/p&gt;
&lt;h2&gt;3. Make: best for visual workflows and handling failures&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;The job:&lt;/strong&gt; a process with several paths, where you decide exactly what happens when a step fails.&lt;/p&gt;
&lt;p&gt;Make calls a workflow a scenario. You build it by connecting modules (each module is one step), and the paths data can take are drawn as dotted lines between them. When a step fails, an error handler can retry it, ignore it, or roll back what the earlier steps changed, where those apps support it. Make can also save an unfinished run so you can retry it later (that setting is off until you turn it on).&lt;/p&gt;
&lt;p&gt;Make&amp;#39;s AI agents can use Make&amp;#39;s AI provider on all plans, so you do not need an account with OpenAI or Anthropic. On paid plans you can connect your AI account instead and pay that provider for the AI use.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Price:&lt;/strong&gt; Make bills in credits, and what a credit costs depends on the plan. Make&amp;#39;s pricing page did not load when we checked, so this post gives no Make prices. For most apps, each module run is one credit, so a ten-step scenario uses ten credits each time it runs. AI steps on Make&amp;#39;s provider are charged by how much text they read and write.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Where it falls short:&lt;/strong&gt; paying per step adds up on long workflows. Checking an app for new data counts as an operation too, so a scenario that checks often uses credits even when nothing new has arrived.&lt;/p&gt;
&lt;h2&gt;4. Activepieces: best for open-source automation you host&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;The job:&lt;/strong&gt; you want to host the tool yourself, or start on a free plan with no card.&lt;/p&gt;
&lt;p&gt;Activepieces is open source, and all plans, the free one included, can run on its cloud or on servers you run. The Free plan gives 1,000 credits a month for up to 5 users, with no card and no time limit.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Price:&lt;/strong&gt; Plus is $20 a month for 10,000 credits, then $0.007 a credit. One run costs one credit, however many steps it has. AI steps cost 2, 10 or 20 credits, depending on the model, unless you connect your AI account on Plus or above, which brings each AI step down to 1 credit.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Where it falls short:&lt;/strong&gt; it connects to fewer apps than Zapier, more than 770 by its count against Zapier&amp;#39;s 9,000-plus. Putting it inside your product under your brand (its Embed plan) starts from $36k a year.&lt;/p&gt;
&lt;h2&gt;5. GoHighLevel: best for local-business marketing in one system&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;The job:&lt;/strong&gt; you run marketing for local businesses and want one system for contacts, campaigns, booking, texting and websites.&lt;/p&gt;
&lt;p&gt;GoHighLevel says it replaces a business&amp;#39;s customer records, funnel builder, email marketing, appointment scheduler, text marketing and review tools. Each client gets a sub-account, and all plans start with a 14-day free trial.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Price:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Starter: $97 a month for 3 client sub-accounts.&lt;/li&gt;
&lt;li&gt;Unlimited: $297 a month for unlimited sub-accounts, with a desktop app that shows your logo to clients.&lt;/li&gt;
&lt;li&gt;Founder: $497 a month, which adds SaaS mode (selling GoHighLevel to clients as your own software). The page&amp;#39;s questions call this the Pro plan.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Texts, calls, email and AI are charged on top.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Where it falls short:&lt;/strong&gt; most of its core features are marketing tools, such as funnels, ads, social posts, reviews and email and text campaigns. Extras add up. A branded client portal app is $49 a month per sub-account, and the HIPAA compliance add-on is $297 a month. If your work is building automations and proving they run, you pay for a lot you will not use.&lt;/p&gt;
&lt;h2&gt;Also worth knowing&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;AI-first tools.&lt;/strong&gt; Lindy and Gumloop are built around AI agents. Lindy&amp;#39;s paid usage starts at $49.99 per user per month, with 5,000 credits each, and Lindy waits for approval before anything with outside impact, such as sending an email. Gumloop Pro is $37 a month for 20,000 credits, with unlimited seats and a 14-day free trial.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tools can disappear.&lt;/strong&gt; Relay.app shut down in September 2026 and permanently deleted all accounts, workflows and run history. Whatever you choose, keep a written record of what each client&amp;#39;s automation does, so you can rebuild it anywhere.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;How to choose&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;You need one unusual app connected fast:&lt;/strong&gt; Zapier.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You need several paths and careful handling of failed steps:&lt;/strong&gt; Make.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You want to host it yourself:&lt;/strong&gt; n8n or Activepieces.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You run marketing campaigns for local businesses:&lt;/strong&gt; GoHighLevel.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You build automations for clients and need them to see it working every month:&lt;/strong&gt; Thrum.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A sensible setup uses two tools. One handles the odd connection. The other is where each client&amp;#39;s work runs, is watched and is shown to them, and that is the job we built Thrum for.&lt;/p&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Choose by the job. Each tool here beats n8n at one thing.&lt;/li&gt;
&lt;li&gt;For client work, the deciding question is what the client sees and who hears first when something stops.&lt;/li&gt;
&lt;li&gt;Thrum&amp;#39;s answer is a portal, a report on the 1st, and alerts that come to you first. Its trade-offs are fewer apps than Zapier, no self-hosting, and a portal, report and alerts that are built and not yet used by any customer.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Checked on 15 November 2026.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;n8n pricing: &lt;a href=&quot;https://n8n.io/pricing/&quot;&gt;https://n8n.io/pricing/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Zapier pricing: &lt;a href=&quot;https://zapier.com/pricing&quot;&gt;https://zapier.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Make, credits: &lt;a href=&quot;https://help.make.com/credits&quot;&gt;https://help.make.com/credits&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Activepieces pricing: &lt;a href=&quot;https://www.activepieces.com/pricing&quot;&gt;https://www.activepieces.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;GoHighLevel pricing: &lt;a href=&quot;https://www.gohighlevel.com/pricing&quot;&gt;https://www.gohighlevel.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Lindy pricing: &lt;a href=&quot;https://www.lindy.ai/pricing&quot;&gt;https://www.lindy.ai/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Gumloop pricing: &lt;a href=&quot;https://www.gumloop.com/pricing&quot;&gt;https://www.gumloop.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Relay.app shutdown notice: &lt;a href=&quot;https://www.relay.app/&quot;&gt;https://www.relay.app/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content:encoded></item></channel></rss>
