The account plan, the segment report, the pre-call brief and the sequence draft belong in a document your team can edit; connected to Google Docs, the agents write them there, sourced line by line.
Some deliverables are prose: the plan for a target account, the report on which segment of the customer base deserves the next quarter, the talking points for tomorrow’s calls. Connected to Google Docs, the agents write those documents directly, with every figure traced to the tool call that produced it and every claim about a company linked to its source.
Sequence drafts and first touches land the same way when you want to review copy in a document before it goes near an outreach tool, and standing missions can keep a living document current: the weekly signal digest, the territory summary, the ICP definition as the data moves.
Firmographics, stack, funding, news, relationships and the angles that matter, written as a shareable brief.
Analysis over any list, with charts embedded and the rows behind them linked.
Openers, talking points and multi-step sequences in a document for review before loading.
Digests and summaries updated on cadence by a standing mission.
Real missions from the playbook library - run them as-is from the console, or read the full article behind each.
Map the buying committee at <company.com> for a <product category> purchase: the economic buyer, the technical evaluator, the champion and the procurement contact, with t…
Segment my HubSpot contacts by lifecycle stage, create a Meta custom audience per stage (MQL, SQL, opportunity) on my connected ad account, and give me a targeting note p…
For the 30 accounts on my calling sheet <name>, prepare call notes: what the company does, size, stack, latest signal, likely objections and the one question to open with…
For my call with <company.com> tomorrow, write a one-page brief - who they are, stack, hiring, funding, likely objections and three questions to ask - schedule the Zoom, …
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.
Yes. A document with an ICP description, a target-account list or a value proposition becomes the brief for a mission.
Inline, as links to the page, filing or record the claim came from, with the mission transcript holding the full trail.
Point the mission at a template document and it follows the structure, filling the sections it can and flagging the ones it cannot.
One connection, autonomous AI agents, one budget ledger - and your approval policy on everything outbound.