Send email notification
Add an email alert to an Attio workflow. Choose who should receive it and include the details they need to take the next action.
Inputs
Install and connect Email Notifications, then add Send email notification in Attio's workflow editor. All three inputs are required.
| Input | What to supply |
|---|---|
| Recipient | An active member of your Attio workspace. Pick a member or use an Attio workspace member supplied by an earlier step. |
| Subject | The alert's subject. Your organization's subject prefix is added automatically. |
| Message | Plain text. Write several lines and insert values from earlier steps. Line breaks are preserved. Paste any record URL directly into the message; it is sent as text. |
Keep the subject and message concise, and link to the Attio record for additional context.
Recipient takes an Attio workspace member, not their email address or a People record. If you have an Attio workspace member ID or email address, use the Find workspace member step from Automations, then pass its Member output into Recipient.
An organization admin configures one optional BCC address in Neon Deer settings. It receives a copy of every alert your organization sends and is not an input on each workflow step. The BCC copy does not count as an additional alert.
The Queued outcome
The step completes with Queued as soon as Neon Deer accepts the alert. Connect later workflow steps to that outcome to continue without waiting for delivery.
Queued has no output fields and does not confirm sending or inbox delivery. A later cancellation, expiry, or sending failure appears in the Activity in Neon Deer; it does not change an already completed workflow step.
If Neon Deer refuses the alert, the step shows an error instead. For example, alerts may be turned off or sending may be temporarily unavailable. Check the message and your sending settings before trying again.
Example: notify the AE about a product signup
A SaaS company tracks product signups in Attio. Its workflow creates a deal, finds the signup's company country, and assigns an AE using a territory lookup table. Add an email alert after the assignment so the AE has the context to follow up.
- Finish the routing first. Use your workflow's company and country data with a lookup table to choose the territory and AE. For example, a company in Germany routes to your EMEA owner.
- Set Recipient. Supply the assigned AE as an Attio workspace member.
- Write the alert. Use a subject such as
New product signup: Acme. In the message, include the person's name, company, signup context, and deal link using the values from your workflow. - Continue after Queued. Use the outcome to continue the handoff. If the original SDR also needs an alert, add another
Send email notificationstep with that Attio workspace member as its recipient.
An example message for the AE:
Sam at Acme signed up for the product.
Territory: EMEA. You are the assigned account executive.
Jamie is the SDR who has been working the account.
Review the signup and coordinate the follow-up with Jamie.
Deal: include the deal link from your workflow.
Use two steps when notifying two different members. Each creates its own alert. Review the organization's sending preferences when deciding how often to notify teammates.
If the alert is not accepted
Read the error on the workflow run in Attio. Check the app's connection, confirm the recipient is an active Attio workspace member, and ask an admin to check Email Notifications settings.
Retrying the same step execution never sends a second email. Starting a separate workflow run can create a new alert, so check Activity before doing that. See Troubleshooting for messages and recovery steps.