CRM
Route Intercom feature-request friction into Linear and link the Attio account
When an Intercom conversation closes, the workflow detects feature-request or missing-capability friction, deduplicates against existing Linear issues.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation closedIntercom
- ActionDetect feature request and extract capabilityOpenAI
- LogicEnd run if not a feature request
- ActionSearch Linear for matching issueLinear
- ActionAppend account or create new Linear issueLinear
- OutputLink issue to Attio company recordAttio
What it does
This workflow captures the specific friction of customers asking for things the product does not do yet. On each closed Intercom conversation it classifies whether the thread is a feature request or missing-capability complaint, searches Linear for a matching open issue, and either adds the requesting account to that issue's demand list or creates a new issue — then links it to the account's Attio record so owners can see what each customer is waiting on.
When to use it
Run this when product feedback arrives through support but never reaches the backlog, and you want demand tied to real accounts for prioritization. Ideal for product and CS teams that prioritize by customer pull.
How it works
- 1An Intercom conversation closes and triggers the run.
- 2An LLM decides whether the thread is a feature request and extracts a normalized capability description.
- 3A logic branch ends the run for non-feature-request threads.
- 4The workflow searches Linear for an existing issue matching the capability.
- 5It appends the account to the matched issue or creates a new Linear issue if none exists.
- 6It links the Linear issue to the Attio company so the request shows on the account.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect AttioReal-time CRM with structured data + powerful views.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
Backfill Intercom conversation topics onto stale HubSpot contacts
Finds HubSpot contacts with no recent Intercom topic, pulls their conversation history from Intercom, classifies the dominant topic with OpenAI.
Daily orphaned-opportunity sweep with manager Slack digest
Each morning this scans Salesforce for open opportunities owned by inactive users and posts a per-manager digest in Slack listing the orphaned deals that need a new owner.
AI-Personalized Dormant Account Win-Back
On a dormancy anniversary, an agent researches the account's history and recent public signals, drafts a genuinely personalized win-back email.
Dormant Account Anniversary Re-engagement Email
Each day, finds Attio accounts whose last activity was exactly N months ago and sends each owner's contact a personalized re-engagement email from Gmail.
Dormant Account Check-In Call Scheduler
On the anniversary of an account's last touch, books a tentative check-in call on the owner's Google Calendar and emails the contact a scheduling invite.
Weekly Dormant-Anniversary Cohort Digest
Every week, groups dormant Attio accounts by which last-touch anniversary they hit that week, builds a prioritized digest.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
