When a list becomes work, it belongs in Asana: routed accounts as tasks for the right owner, signal alerts as tickets with the evidence attached, and cleanup batches tracked to done, all created by the missions that produced them.
A hot account is only useful if someone owns the next step. Connected to Asana, prospecting and signals missions create tasks in the project you name: the account, the contact, the signal that qualified it and the suggested action, assigned to the owner your routing rules say. The list stops being a spreadsheet nobody opens and becomes a queue people clear.
Operational work rides the same connection: a CRM hygiene sweep becomes a batch of merge tasks, an enrichment run with unresolved rows becomes a research task, and the mission that opened the task closes it when the follow-up run confirms the fix.
Routed accounts created as tasks with contact, signal and next step, assigned by your rules.
Funding, hiring and job-change events from a watch created as tasks with the evidence attached.
Merge, suppression and research work from hygiene sweeps as tasks the team can clear.
A later run confirms the fix and completes the task it opened.
Real missions from the playbook library - run them as-is from the console, or read the full article behind each.
Report coverage across the target accounts on list <name>: how many have a verified contact, a buying committee of three or more, a live signal this quarter and an owner …
Connections are scoped to one workspace, every card has a disconnect button, and outbound actions honor your approval policy.
Support: questions or trouble with this integration reach a human at hello@astrofabric.ai - no account needed. Platform status: status.astrofabric.ai.
By the routing rule in the objective: territory, segment, round-robin or a named owner. The rule is stated in the deliverable so assignments can be audited.
Materiality thresholds you set decide what becomes a task and what waits for the digest. A quiet week creates nothing.
Yes. The signal, the source and the date sit in the task description with links to the mission transcript.
One connection, autonomous AI agents, one budget ledger - and your approval policy on everything outbound.