What changed
Lookup tables let Attio workflows retrieve reference data without a separate branch for every possible value. Update the table as your team and routing rules change.
Named-account routing
When certain accounts belong to specific reps, a workflow can accumulate a branch for every exception. Put those assignments in a table instead:
| Company domain | Account owner | Slack ID | Territory | Priority |
|---|---|---|---|---|
| acme.example | Alex | U01ALEX01 | North America | High |
| beacon.example | Sam | U01SAM001 | EMEA | Standard |
| cedar.example | Jordan | U01JORD01 | North America | Standard |
Store the owner as a workspace-member field so Attio can use it in an assignment step. Pass the other outputs to record updates or notifications. If no row matches, follow your normal routing path.
When an account changes hands, edit its row instead of finding and updating the right branch in a workflow.
Other examples
The same pattern works for a territory-to-team mapping, a primary rep's backup, or a source value that needs a consistent label. For example, map both Software and SaaS to Technology before an Attio step updates the industry field. Each input gets its own row, so the mapping is easy to inspect and change.
Each lookup matches one unique field and can return several values. Employee-count ranges, wildcard fallbacks, and multi-condition routing still need workflow logic; the table does not evaluate those rules for you.
Mention the right people in Slack
Say a deal needs a Slack alert that mentions both its account executive and SDR. With three AEs and six SDRs, there are 18 possible pairings. Maintaining a separate branch for each pairing would turn a simple notification into a lot of workflow upkeep.
Add each person's Slack ID to the Workspace members table. In your Attio workflow, look up the AE and the SDR, then use their Slack mentions in the same message:
The lookups supply the mentions; your Slack message step sends the alert. Reuse the same steps for different AE and SDR pairings, without hard-coding their Slack IDs in a custom code block or creating a branch for every combination. If someone's Slack ID changes, update their table entry.
You can also add time zones, departments and other team details for workflows to look up.