To send AppSheet notifications by email when a job status changes, create a bot on your Jobs table with an update event, add a condition that compares the status before and after the edit, then add a Send an email task that takes the recipient from a column in the row. Deploy the app first, or the emails will reach only you.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThree details separate a working alert from a noisy or silent one. Test mode sends every email to the app creator only, free accounts can email only the owner, and a bot without a before-and-after condition fires on every edit to the row, not only on the status change you care about.
Which job status changes should trigger an AppSheet email?
Send an AppSheet email only for the status changes that matter to the person receiving it, because an email for every change would train clients to ignore the practice. Take a six-person accountancy practice with year-end accounts jobs moving through five statuses: Received, In progress, Query with client, Ready for review and Filed. Four are worth sending:
| New status | Who gets the email | Purpose | Attachment |
|---|---|---|---|
| Received | The client | Confirms the documents arrived and states the next step | None |
| Query with client | The client, CC the preparer | Asks the specific question, so the job can restart | A one-page list of the open queries as PDF |
| Ready for review | The reviewing partner | Tells the reviewer the file is waiting | None |
| Filed | The client | Confirms completion and attaches the filed summary | PDF summary |
In progress gets no email: it is an internal status, and sending it would only generate replies asking when the job will finish. That choice, which statuses are customer-facing and which are internal, is the most useful decision in the whole build. A simple test is whether the recipient has to do something or can stop worrying. If neither, skip the email.
Which columns does the Jobs table need before you build the bot?
The Jobs table needs every column the alert will read, because an AppSheet alert can only use data that exists in the row. Check that the Jobs table has these columns before you open the Automation tab:
- Status, an Enum column with exactly the values above. Typed free text will break the condition the first time someone writes "in-progress".
- Client email, an Email column, filled or referenced from a Clients table.
- Preparer email and Reviewer email, also Email columns, so you can email staff by role.
- Query text, a LongText column the preparer fills when the status is Query with client.
- Last emailed status, a Text column the bot will write to as a guard against duplicates (explained below).
If client details live in a separate Clients table, make Client a Ref and reach the address through the reference, for example [Client].[Email]. AppSheet's email help gives this as a recipient pattern: a field in a referenced record. That keeps one address in one place, so a correction applies to every future email.
If you want to build the Jobs sheet and its status columns yourself, try The Complete Excel Course with AI Integration on Coding Liquids.
How do you build an AppSheet bot that sends an email?
To email people from AppSheet, go to Automation in the editor and create a bot with an event that starts it, optional conditions, and a process made of steps and tasks, following AppSheet's help.
- Event: choose a data-change event on the Jobs table and set it to Updates only, since you care about changes to an existing job.
- Condition: add the expression in the next section, so the bot runs only when the status changed to the value you want.
- Task: add a Send an email task. Set Email type to Custom template and the table to Jobs.
- Recipients, subject and body: fill them in using column values.
- Save and use Preview email to see the first row of the table rendered.
Make one bot per customer-facing status rather than one bot with many branches. Four small bots are easier to read, switch off and test than one that does everything. Name them for what they do, such as "Email client - Query" and "Email partner - Ready for review".
Which condition fires an AppSheet email only on a real status change?
An AppSheet email fires only on a real status change when its condition compares the row after the edit with the row before it. AppSheet gives you two references for this: [_THISROW_BEFORE] is the row as it was before the edit, and [_THISROW_AFTER] is the row afterwards. Google's help shows the pattern for "send an email when a row is updated to have a specific column value":
AND(
[_THISROW_AFTER].[Status] = "Query with client",
[_THISROW_AFTER].[Status] <> [_THISROW_BEFORE].[Status]
)
The first line says the new status is the one you want. The second line says it was something different a moment ago. Without the second line, any later edit to that row, such as correcting the query text, would send the email again while the status still reads Query with client.
For one bot that covers two statuses, use OR inside the first test:
AND(
OR([_THISROW_AFTER].[Status] = "Received", [_THISROW_AFTER].[Status] = "Filed"),
[_THISROW_AFTER].[Status] <> [_THISROW_BEFORE].[Status]
)
Keep to one status per bot unless the emails would be identical. If the wording differs between statuses, a single bot needs conditional text in the body, which is harder to maintain than two separate templates.
How do you write an AppSheet email that clients understand?
Write the subject and body of an AppSheet email with text and variables between double angle brackets, such as <<[ClientName]>>, so clients see only what they need. The email task accepts text, variables and expressions in both. Compare two versions of the query email.
Before, the default: subject "Update to application Jobs", body a table of every column in the row. Clients see internal fields and cannot tell what is being asked.
After, a custom template (illustrative):
Subject: We need one answer to finish your accounts, <<[Client].[Name]>>
Hello <<[Client].[FirstName]>>,
To keep your year-end accounts moving we need an answer to this:
<<[Query text]>>
Reply to this email with the answer or attach any document we asked for.
We will restart the work as soon as it arrives, and your target filing
date of <<[Filing deadline]>> is unchanged.
<<[Preparer name]>>
Two settings make that email usable. Reply To defaults to noreply@appsheet.com, so set it to the preparer's real address or a shared mailbox, or a client's reply goes nowhere. And Customize From name lets you replace the default sender text, which is otherwise the app creator's address. Check both in the Advanced section of the task before you switch the bot on.
How do you take AppSheet email recipients from columns?
AppSheet can take email recipients from columns instead of typed addresses, and its help lists five ways to fill To, CC and BCC, each with a use here:
| Pattern | Example | Use in the practice |
|---|---|---|
| A specific address | "accounts@example.com" | A BCC to a shared mailbox, so every client email is archived |
| A column in the changed row | [PreparerEmail] | CC the preparer on the query email |
| A column in a referenced row | [Client].[Email] | The client's address from the Clients table |
| An entire column of another table | Partners[Email] | Tell all partners when something is overdue |
| Selected rows of another table | SELECT(Staff[Email], [Role] = "Reviewer") | Tell every reviewer, without hard-coding names |
Filled in for the practice's Query with client bot, the three recipient boxes read as follows (illustrative column names):
To: [Client].[Email]
CC: [PreparerEmail]
BCC: "filed-emails@example.com"
The BCC is a shared mailbox the practice owns, so a partner can search every client email later without being copied on each one. It also means that when a client says they never received a message, you can prove what was sent and when.
If an address contains a hyphen or a plus sign, AppSheet says to wrap it in quotes. And if a client's Email cell is blank, the email has nowhere to go: add a Required rule to the column, or a condition that skips the bot when the address is blank, such as ISNOTBLANK([Client].[Email]) joined into the AND above.
If you see an OutgoingEmailAllowListViolations error in Audit History, either your team admin has restricted the recipient list for outgoing email or your Workspace setting blocks external recipients. Ask the admin to widen the list. That is a policy block, not a bug in your bot.
Attaching a PDF to the "Filed" email
In the same task, expand Attachment settings. The content type defaults to PDF, and the options also include CSV, HTML, ICS calendar, JSON, XLSX and XML. For the practice's filing confirmation:
- Create a document template (AppSheet's help covers using templates in a bot) with the client name, the period, the filing date and the status.
- Choose it as the Attachment Template and set the Attachment Name, for example
Filed summary <<[Client].[Name]>>. - Choose Attach and archive, so a copy is saved while the client receives one. Archive options also include archive without attaching, which suits large files where you send a link instead.
- Set page size and orientation if the default does not suit.
Archived attachments go to the authentication provider's file system by default, which is Google Drive for a Google sign-in, in a folder called Attachments unless you set another path. Filenames get a timestamp appended by default. Leave that on: AppSheet warns that with it disabled, a repeated name overwrites the earlier file.
If your firm does not want staff attaching files in automations at all, an admin can set the Restrict Automation Email Attachments policy. Know this before you build, because a policy can switch off a feature you just configured. Related reading: the field service app tutorial builds a job-sign-off PDF the same way.
How do you stop AppSheet sending the same email twice?
AppSheet sends the same email twice when a status is set, changed back and set again, because the before-and-after condition counts each as a real change. Picture the accounts: a preparer sets Query with client by mistake, notices, changes it back to In progress, and sets it again. The before-and-after condition sees three real changes and fires twice for the query status. The client gets two emails, five minutes apart, with the same question. This is the most common complaint about status alerts.
The guard is the Last emailed status column. Add a step after the email in the same bot to write the status into that column, using AppSheet's data-change action, and extend the condition with [_THISROW_AFTER].[Last emailed status] <> [_THISROW_AFTER].[Status]. Now the email can go only once per status, however often the status is toggled. If a status can legitimately repeat (a second query later in the job), clear the guard column when the status moves forward past Query with client.
Letting the reviewer act from the email itself
For internal alerts there is a second email type. AppSheet's help lists two: Custom template, which this tutorial has used, and Embedded app view (dynamic), which embeds supported app views in the message so Gmail recipients can interact with the app from their inbox without leaving it. For the practice's Ready for review email, that means the partner could open the job's detail view in the message, read the notes and tap an action such as Approve or Send back. It suits internal staff on Gmail better than clients, who may not use Gmail or have an app licence. Check the setup in AppSheet's help for embedded emails before you promise it to a team, and keep a plain custom-template fallback for anyone who reads mail elsewhere.
Subject lines that get opened
The default subject, built from the app and table name, is useless to a client. Compare these for the same Query with client email (illustrative):
| Subject | Verdict |
|---|---|
| Update to application Jobs | Default; reads like spam |
| Job 1042 status changed | Internal language; says nothing about what to do |
| One question about your accounts | Clear, short and asks for action |
| We need one answer to finish your accounts | Better: says the benefit of replying |
Why is my AppSheet email not arriving?
An AppSheet email most often fails to arrive because the app is still in test mode, and the table below links each symptom to its likely cause. Two causes sit outside it: a status typed straight into the spreadsheet does not trigger a bot, and accounts created after 4 May 2026 can usually email only their own domain.
| Symptom | Likely cause | Where to look |
|---|---|---|
| Only you receive emails | App in test mode, or free account | Run the deployment check; confirm your plan |
| Bot never fires | Condition never true, often a typo in the status value | Compare the Enum value with the string in the condition |
| Fires on every edit | No before-and-after comparison | Add the second line of the condition |
| Fails for external recipients | OutgoingEmailAllowListViolations policy | Audit History; ask the admin |
| Replies bounce or vanish | Reply To left at noreply@appsheet.com | Advanced settings of the task |
| Works for some clients only | Blank or malformed email cell | Add a Required rule and a blank-skip condition |
What are AppSheet's email limits for each plan?
AppSheet limits how many email recipients an app can reach each hour and each day, and the limit depends on your plan, according to its automation limits page. The limits are:
| Limit | Free | Starter, Core, Publisher Pro | Enterprise Plus |
|---|---|---|---|
| Email recipients per hour | 5 | 200 to 400 | 25,000 |
| Email recipients per day | 30 | 1,000 to 20,000 | 50,000 |
Daily limits reset once a day (the limits page gives the exact time). Do the practice's sum using the four emails in the table above: client; client plus the preparer on CC; the partner; the client again. That is five recipients per job, so 60 jobs a month is 60 x 5 = 300 recipients, about 14 a working day. That is far below the paid floor of 1,000 a day, although the free plan's own limits of 5 an hour and 30 a day, and its owner-only rule, make it unusable for clients. A firm sending reminders to hundreds of clients on one day is different: at 200 an hour, a 1,000-recipient batch takes five hours to clear, so spread bulk sends across the day.
Email is a Starter feature (automated emails are ticked on every paid tier), but in practice the free plan's 5-an-hour cap makes it unusable for customers. If you are choosing a plan, AppSheet's pricing explained compares tiers, and Core's $10 per user a month (or nothing if your Workspace edition includes it) is the usual choice once barcode, roles or scheduled events matter.
Can AppSheet send email from your own address?
Yes: by default automation emails come from noreply@appsheet.com unless you change the From name, but AppSheet's Bring Your Own Email, a public preview from September 2026 and generally available since November 2026, lets you send from your own Workspace or Gmail address. In the Send an email task you click Select an account under From, authorise your Workspace or Gmail account and pick the sender. Google's help says users on a company domain can send from addresses or aliases on that domain or on their organisation's owned domains, users on public domains such as gmail.com only from their AppSheet login address, and that support for Microsoft accounts is planned for early 2027. Only the app owner can set the From address. AppSheet highly recommends a custom address over the default and says it helps prevent emails being flagged as spam.
It is a new feature, so test with a handful of real messages and read the replies before you rely on it for client mail. If it is not available to you, a clear From name and a monitored Reply To are the fallback.
In what order should you test AppSheet email alerts?
Test AppSheet email alerts by previewing the email, running the bot test, deploying the app, changing a test job's status and then toggling it twice to confirm only one email arrives.
- Preview the email in the task to see variables rendered for the first row.
- Use the bot testing feature from the editor, which triggers the automation without a live edit.
- Deploy the app by running the deployment check. Until then, as AppSheet says, messages go only to the creator.
- Edit a test job that has your own address as the client's, change its status, and read the arriving email on a phone.
- Open Audit History to confirm recipients, since the help directs you there to see whether an email was delivered.
- Toggle the status twice and confirm only one email arrives.
The step people skip is the last. The duplicate bug appears only when you try to cause it.
Which deploy-day mistake stops AppSheet emails reaching clients?
Forgetting to deploy the app stops AppSheet emails reaching clients, because every test sent while the app is in test mode goes only to the creator. Suppose the practice builds the four bots, tests each by changing a status, and sees emails arrive. Everything looks right. They tell the team it works. A week later nobody has had a client reply. The tests all went to the creator because the app was never deployed, so the client address was ignored every time. The fix is a five-minute deployment check and a second test with a real colleague's address in the client field. Make "send a test to a colleague, not to me" the last item on the launch list.
Related builds: generating the job tracker with Gemini gives you the tables to attach these alerts to, and Airtable versus AppSheet compares the automation side if you are still choosing. Start with one bot for the status that costs you most phone calls, run it for two weeks, and add the next only when the first is quiet and correct.
If you want help fitting alerts like these into how your practice actually runs, I offer one-to-one AI consultations for small businesses.
AppSheet email alerts: questions answered
Why do my AppSheet emails only reach me?
Because the app is still in test mode. While an app is in test mode, which means you have not run a deployment check and deployed it, AppSheet sends every message to the app creator only. On a free account, email can also go only to the owner. Deploy the app, then check Audit History to confirm the real recipients.
Can the email go to the address stored in the row?
Yes. In the To field, enter the column name, such as [CustomerEmail], or a referenced column such as [CustRef].[Email]. You can also point at a whole column in another table, or a selected set of rows, to reach a staff list.
How many emails can an app send?
It depends on your plan. AppSheet's automation limits page gives free accounts 5 recipients an hour and 30 a day. Starter, Core and Publisher Pro get 200 to 400 an hour and 1,000 to 20,000 a day, and Enterprise Plus 25,000 an hour and 50,000 a day. The limits count recipients, so CC and BCC addresses count too.
Can I send from my own address instead of noreply?
Yes, from a Workspace or Gmail account. AppSheet's Bring Your Own Email, a public preview from September 2026 and generally available since November 2026, lets the app owner pick a sender under From in the Send an email task. Company-domain users can send from addresses on their organisation's domains, gmail.com users only from their AppSheet login address, and Microsoft account support is planned for early 2027.
How do I stop AppSheet sending the same email twice?
Add a Last emailed status column. Write the status into it with a step after the email, using AppSheet's data-change action, and extend the bot's condition so the email can go only once per status, however often the status is toggled. Clear the column when the status moves forward if a status can legitimately repeat.
Can AppSheet email clients outside my company's domain?
It depends on when your account was created. AppSheet's help says accounts created after 4 May 2026, outside a Workspace organisation that existed before then, can email only addresses on their own sign-in domain, and gmail.com accounts only their own address. Older accounts are exempt, and a Workspace account can reach outside addresses by sending through Bring Your Own Email.
Why does changing the status in the spreadsheet not send an email?
Because AppSheet's help says changes made directly to the data source, such as typing in the Google Sheet, do not go through the AppSheet server, so they do not trigger bots. Change the status in the app, or set up AppSheet's Google Sheets add-on, which can trigger bots on direct edits.
Further reads
- How to Use AI for Print Proof Approvals and Job Status Updates — Job-status updates in a printing business.
- Google AppSheet for Nonprofits: Volunteer Rota App Without Code — Another AppSheet build with email reminders.
- How to Build an AppSheet Inventory App With Barcode Scanning — A low-stock email built on the same bot pattern.
Browse all AI-for-business tutorials
Sources: AppSheet help-centre articles on sending email from automations, automation limits, subscriptions and Bring Your Own Email, read on 17 Nov 2026.
