Email is where a list meets the outside world; connected to Gmail, the agents write first touches from each row’s evidence, create them as drafts for review, deliver finished lists and digests, and send only what your approval policy allows.
The last step of most missions is an email someone has to write. Connected to Gmail, that step closes: a prospecting list becomes a draft per contact grounded in the hiring, funding or technology signal that qualified them, a signal watch becomes a Monday digest in your inbox, and a finished list arrives as an attachment to the person who asked. The drafts read like a person wrote them because a person set the rules they were written under.
Sending is the most audited write in the platform: every outbound message honors the approval policy, the audit log records what went to whom, and your brand kit shapes every draft. Autonomy over email is earned through exactly this much control.
A first touch per contact written from the signal that qualified the account, created as a Gmail draft with the evidence noted for review.
Standing missions send the second and third touch on schedule to contacts who have not replied, with silence respected as an answer when you configure it so.
Finished lists, coverage reports and signal digests mailed to stakeholders when missions finish, the loop closed without a copy-paste.
Responses to a sequence classified and written to the CRM as outcomes, with interested replies routed to the owner.
Real missions from the playbook library - run them as-is from the console, or read the full article behind each.
Go through every company in HubSpot missing employee count, industry or HQ, fill the fields through the enrichment waterfall, write them back to the records, and email me…
Find the companies showing buying intent on <topic> this week, rank them by intent score and momentum, keep the ones matching our ICP, add the likely buyer with a verifie…
Verify every email on list <name>, flag risky and catch-all addresses separately from the deliverable ones, dedupe on email and domain, push only the clean rows to HubSpo…
For the companies on list <name> that are hiring a <role>, write a two-line opener per contact that quotes the posting's actual language and connects it to what we do, an…
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.
Only under a policy you set. Gated is the default posture for teams starting out: every send waits with recipient, subject and body shown. Teams open it once trust is earned, and the audit log records everything either way.
Missions read what their objective requires: the thread with a prospect, the label you point them at. Access is workspace-scoped, actions are logged, and disconnecting revokes it all.
The brand kit and your saved preferences shape every draft, and corrections stick: edit an agent draft harshly once and workspace memory learns the register you actually send in.
One connection, autonomous AI agents, one budget ledger - and your approval policy on everything outbound.