Export AI-Personalized Content Directly into Outreach Custom Fields

Why Custom Field Export Beats Template Replacement

Traditional integrations modify your sequences or inject content by replacing template text. Autobound takes a fundamentally different approach: it writes AI-personalized content into Outreach's 35 built-in custom fields ({{custom1}} through {{custom35}}), and your sequences simply reference those fields as variable tokens. Your sequence templates stay exactly as you built them -- the personalization flows through the data layer, not the template layer.

This architecture preserves everything Outreach does well. Sequence analytics, A/B testing, step-level reporting, and deliverability monitoring all work exactly as they always have, because Outreach is still rendering and sending every email natively. There is no shadow system, no sequence duplication, and no content replacement happening behind the scenes.

How Custom Field Mapping Works Under the Hood

Outreach provides 35 custom fields on the Prospect object: {{custom1}} through {{custom35}}. When you configure the Autobound integration in AI Studio, you map each content output to a specific custom field. For example, you might map the AI-generated subject line to {{custom25}} and the email body to {{custom26}}. For multi-step sequences, you can map Step 2's subject to {{custom27}} and body to {{custom28}}, and so on.

In your Outreach sequence, you build email steps that reference these variables. When Autobound exports personalized content for a prospect, it populates the custom fields via the Outreach API. Outreach's trigger-based enrollment detects the field update and automatically adds the prospect to the appropriate sequence. The email renders with the AI-generated content pulled from the custom fields, and sends from the sequence owner's account with their signature, tracking settings, and sending schedule.

Because custom fields persist on the Prospect object, they can be referenced by any sequence, template, or snippet in Outreach. A single export from Autobound can feed content to multiple sequences simultaneously -- first-touch, follow-up, re-engagement, and event-triggered sequences can all pull from the same set of personalized fields.

Multi-Channel Content Through Custom Fields

Custom fields are not limited to email content. Autobound generates personalized LinkedIn messages, call scripts, and video outreach scripts, all of which can be mapped to dedicated custom fields. A rep working through a multi-channel Outreach sequence can see AI-personalized talking points for a call step by referencing {{custom30}}, or a tailored LinkedIn connection request in {{custom31}}.

Every piece of content is generated from the same 400+ real-time buyer signals -- funding rounds, executive hires, technology stack changes, earnings call themes, job postings, shared connections, and more. This means the messaging across email, LinkedIn, and phone is thematically consistent, referencing the same signals from different angles appropriate to each channel.

Autopilot Mode vs. Copilot Mode in AI Studio

Copilot Mode generates personalized content for each prospect and presents it for human review inside AI Studio before exporting. Reps see the AI-generated email alongside the specific buyer signals that informed it, and can approve, edit, or reject each message. Once approved, the content is exported to Outreach custom fields and the prospect is enrolled in the sequence.

Autopilot Mode removes the review step entirely. Autobound generates content and exports it directly to Outreach custom fields without manual intervention. Combined with Outreach's trigger-based enrollment, this creates a fully automated pipeline: AI Studio generates content, pushes it to custom fields, and Outreach enrolls and sends -- all without a rep touching anything.

Both modes are available on all Autobound plans, including the free Basic tier. Teams can start with Copilot to build confidence in the AI output, then switch to Autopilot once they are comfortable with the content quality.