Automations

What Automations does

Its triggers start a workflow when a note is edited or deleted, when a task is created, changed or deleted, when a comment or call recording is created, or when a scheduled time arrives. Its steps find notes, tasks and workspace members, read meetings, comments and call transcripts, compare and convert values, create and move notes, create folders, and read lookup tables. It also lets you schedule selected Attio records to run in a workflow at a chosen time.

The app has two parts that run in different places.

What needs a Neon Deer account

Every trigger and step needs a Neon Deer account and the app's Neon Deer connection (steps 1 and 3 of Setup), including blocks that only call Attio. Until the workspace is connected:

Once connected, blocks keep running during a Neon Deer outage or after the connection's access token expires. They stop only when Neon Deer refuses the workspace's access (see Permissions). Lookup tables and scheduled runs also depend on your Neon Deer plan. See Settings → Billing in Neon Deer for what each plan includes.

Setup

1. Create a Neon Deer account at app.neondeerdata.com, or sign in if you already have one.
2. Install the Advanced Workflow Automations app in your Attio workspace. Install it from the Attio Marketplace. Attio lists installed apps under Settings » Apps. The app's triggers and steps then appear in Attio's workflow editor. They run only after the next step.
3. Add the Neon Deer connection. In Attio, open Settings » Apps » Advanced Workflow Automations » Connections. Add a Workspace connection, then approve the Neon Deer consent screen that opens. The app keeps one workspace connection and checks it with Neon Deer before saving it. If the connection is refused, see Connection problems.
4. Finish setup in Neon Deer. Open Automations on the Neon Deer platform. Until the connection exists, it opens a setup page with two steps. Workflow connection is required for the app's triggers and steps to run; its Connect in Attio action opens the same Connections tab as step 3. Workspace access is optional and lets steps look up details from your Attio workspace, like your member list, instead of only what the workflow passes in; a workspace admin turns it on with Connect Attio.
5. Set a workspace time zone. Scheduling records needs one, and it refuses to start without it. In Neon Deer, open Settings » General. Skip this if you will not schedule records.
6. Create lookup tables. The Find lookup table row step reads from them, so create the tables it will use. Skip this if you will not use that step. Creating tables needs a workspace admin, or a member with the Manage Advanced Workflow Automations permission. See Lookup tables.

You do not copy any key or token: Attio stores the connection's access token and refreshes it on the connection's refresh schedule. If the token expires or access is revoked, the app's settings page says so (see Connection problems).

The app's settings page in Attio shows a warning when setup needs attention, and links to your tables and scheduled runs on the platform. It has no settings of its own.

Example: route a product signup and notify sales

A SaaS company tracks product signups in Attio. When a person signs up, the workflow creates a deal, assigns an account executive (AE) based on the associated company's country, and sends a Slack message mentioning both the AE and the sales development rep (SDR) who was already working the account.

In this example, the person's company is in Germany. The country lookup returns EMEA, the territory lookup returns Priya Shah as the AE, and the company's existing SDR is Jonas Meyer.

Prepare the lookup tables

Create the routing tables and share their Territory and AE fields with workflows. In the Workspace members table, fill in each rep's Slack member ID and share Slack mention. Your signup integration should populate the person's Company and the company's country and original SDR before starting this workflow.

Build the workflow

1. Start when the person signs up. Use Attio's Attribute value changed trigger on a People attribute such as Signup status. Continue when the new value is Signed up.
2. Create the deal. Use Attio's Create record block for Deals. Link the person and their company, and copy the company's existing SDR into an Original SDR field on the deal.
3. Find the territory and assign the AE. Add Find lookup table row for Country routing. Set Find by to Country code and pass the company's country code. Use the returned Territory in a second lookup against Territory owners. Pass its AE output into Attio's Update record block to set the new deal's owner.
4. Find both Slack mentions. Look up the Original SDR and the assigned AE in Workspace members, using their workspace member IDs. Each lookup returns that person's Slack mention.
5. Notify both reps. Use Attio's Post message to channel block. Include both Slack mention outputs, the person and company names, the territory, and a link to the deal. Jonas gets the signup context, and Priya gets the deal she now owns.

Check Found after each lookup and check that each Slack mention is filled before posting. If a country, territory owner, or Slack mapping is missing, send the deal for manual review. See lookup outputs and missing matches for the branch configuration.

Example: alert a deal owner about a new form submission

A Form submissions custom object stores incoming responses. A separate process screens out spam and links valid submissions to the right deal, or your team reviews and assigns them manually.

An alert on submission creation would fire before that review and routing is complete. This workflow alerts the deal owner only when a submission is linked to their deal, using that submission's answers. Older submissions remain linked for reference.

1. Watch the deal's Form submissions attribute. Use Attio's Attribute value changed trigger on Deals. It provides the previous and new linked records.
2. Find the newly attached submission. Add Compare records. Set Record object to Form submissions, wire the previous values into Set A and the new values into Set B. Continue only when Only in B → Count is above 0.
3. Find the owner's Slack mention. Use Find lookup table row against the Workspace members table, using the deal owner's workspace member ID. Check Found and that the returned Slack mention is filled.
4. Send the new submission's details. Use Attio's Loop block over Only in B → Records. Inside the loop, post a Slack message mentioning the deal owner, with the current submission's answers, submission time, and deal link. Read the answers from the loop's current record, rather than the deal's full list of submissions.

Attaching one submission produces one alert. Removing a link produces no alert because Only in B is empty. If several submissions are attached together, the loop alerts on each addition. Compare records identifies newly attached records; it does not choose the latest by submission date.

Where to go next

• Triggers: events that start a workflow, with configuration, outputs and examples.
• Steps: actions inside a workflow, with inputs, outputs, behavior and errors.
• Lookup tables: create, import and edit reference data, and read it from a workflow with Find lookup table row.
• Scheduled workflows: send selected records into a workflow at a chosen time, then monitor or cancel the runs.
• Troubleshooting: what errors mean, connection and permission problems, limits, and how to recover.

For what Neon Deer stores and for how long, see the Privacy Policy.