A booking request, an order or a job card lands in a client's Airtable base, and somebody needs an email about it. You can do that with Airtable's own email action, with a general automation tool such as Zapier, or with a Thrum starter that sends through the client's own SendGrid account. Below is what each route does according to its documentation, followed by the Thrum setup from start to finish.
Airtable's built-in Send email action
Airtable automations include a "Send an email" action. You start with the "When record created" 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 "Show more options" adds CC, BCC, a From name and a reply-to address.
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.
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 "When record matches conditions" or "When record enters view" instead.
This action sends the mail from Airtable itself. For an email that leaves from the client's verified SendGrid sender, Airtable's help centre points to the "Run a script" action, which can call outside services with fetch(). Keys belong in the script editor'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's help centre is the place to look for it.
Zapier
Zapier lists a ready-made template called "Send email from SendGrid for new Airtable records", built from Airtable's "New Record" and SendGrid's "Send Email". 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's Free plan it checks for new data every 15 minutes.
Setting it up in Thrum
In Thrum each client is a separate workspace holding that client's keys, so this starter sends from the client's SendGrid and reads the client's Airtable, and you repeat it per client from the same template.
- Install the starter. Open Templates → Library, find "Send an email in SendGrid when a record is added in Airtable" 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.
Connect Airtable. At airtable.com/create/tokens, create a token with the scopes data.records:read and data.records:write, add the client's base to it, and paste it into the checklist.
Connect SendGrid. In the client'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.
Fill in four fields. "SendGrid: From address" takes the sender, for example hello@northside.example. "Who it goes to (SendGrid)" is the address that gets the email, yours or the client's team. "Airtable: Base ID" is the appXXXXXXXXXXXXXX code, and "Airtable: Table" is the table's name, such as Leads.

- Make the email say something useful. As installed, the subject is "A record is added" and the plain-text body has two lines, "A record is added in Airtable." and "Added at:" 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
{{ trigger.payload.fields.Name }}) in the subject and the body.

- Switch it on. 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.
When a send fails
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's inbox, and the run says it may have gone through so you can check and retry it by hand. If the client's Airtable token stops working, the failed checks raise an alert that names the app.
Which one to pick
Airtable's email action is enough when the people being emailed are collaborators or fit inside the plan's daily allowance, and the sender address doesn'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 Airtable and SendGrid page lists the other combinations, including logging SendGrid bounces and link clicks back into Airtable.
Checked on 14 November 2026.
Sources



