Build an AI lead-routing workflow in Attio with Codex browser use
Codex + Chrome computer use + Attio + Slack
New CXO.dev leads can be interested in a course, training for a team, or consulting. Before anyone follows up, we have to read the context and decide who should take it. I had Codex use Chrome to build a draft workflow in Attio, where we keep those leads.
- Gather the deal, company, contacts, and notes so the decision uses the context already in Attio.
- Have an AI step choose an owner using the rules I provided, explain its choice, and flag unclear cases for review.
- Assign the deal and send a short Slack handoff with the context and a link back to Attio.
I described how I wanted leads handled. Codex set up the fields, branches, and message variables in the browser. The goal is for someone to get a lead they can act on without first having to dig through the CRM.
# Draft a lead-routing workflow in Attio
Use computer use in Chrome to configure an unpublished Attio workflow for the lead handoff I describe.
First inspect the existing workflow and show how its steps connect. Use my routing rules and the exact owners I provide; do not invent either.
Configure an agent to read the triggering Deal and its linked People, Company, and Notes. Return one owner, a short reason, a review-needed flag, and one readable lead summary. Use only information supported by the linked context. Mark missing or conflicting information for review.
Order the steps as follows:
1. Enrich the lead context and choose an owner.
2. Update the Deal owner through the appropriate branch.
3. Prepare the Slack handoff with the owner, reason, review flag, concise lead summary, and a direct Attio link.
Check the saved owner fields, message variables, and workflow diagnostics. Keep the workflow unpublished. Report exactly what is configured and what still needs a live test. Do not send test messages or contact leads.