Overview
Clay enables teams to segment, enrich, and manage prospect data efficiently. By integrating Autobound’s API directly into a Clay table as an HTTP API request, users can generate hyper-personalized content based on real-time insights. This setup eliminates the need for generic LLM prompts, leveraging hundreds of rich data signals for better-targeted messaging.
To get started, we recommend using one of the following Clay table templates:
Sequence Table - Ideal for generating multi-step email sequences.
Single Content Item Table - Best for generating a single email, LinkedIn message, or outbound touchpoint.
How the Integration Works
1. Enrich & Segment Data in Clay
Create list of prospects to send hyper personalized messaging too
2. Generating Hyper-Personalized Content with Autobound
Instead of using a generic LLM or prompt inside Clay, leverage Autobound’s API to create highly customized content:
Set up an HTTP API request inside a Clay table that sends structured prospect data to Autobound.
Autobound’s API processes the data and returns messaging tailored to each contact, leveraging 350+ real-time signals.
The content is returned to Clay and stored in separate columns for easy export.
3. Configuring the Sequence Table for Multi-Step Outreach
By default, the Sequence Table generates three email outputs. If users want to create a sequence, it will default to generating emails. However, if they want to include non-email steps (such as LinkedIn connection requests or follow-ups), they can use the contentToRewrite parameter and pass in a connection request template with specific instructions. Instructions can be added using [brackets like this] to guide the AI in structuring the message. Additionally, the additionalContext parameter can be used to further refine non-email touchpoints in the sequence. However, users can modify this by adjusting the numberOfSequencedEmails API parameter, which controls how many email touchpoints Autobound generates per contact
Users can also choose to output multiple independent content options in the Single Content Item Table by adjusting the n parameter. Unlike a sequence, these outputs are independent and not based on the previous step..
Setting Up Autobound’s API in a Clay Table
Autobound can be leveraged as an HTTP API request within a Clay table, allowing users to pass in only the necessary parameters. If a non-required field is left blank, the request will still function, thanks to a built-in formula ensuring flexibility.
1. Understanding Required vs. Optional API Parameters
Before setting up your API call, review Autobound’s API documentation to understand which fields are required vs. optional:
Required Parameters: Must be included for the request to be valid.
Optional Parameters: Provide additional customization but are not mandatory.
🔗 Explore required & optional parameters here:
Autobound API Docs – Generate Personalized Content
🔗 Full List of Parameters:
Autobound API Parameters
2. Key API Parameters to Know
Beyond the required fields, certain optional parameters significantly impact the quality and customization of generated content.
contentToRewrite
Allows users to input existing text they want Autobound to refine or enhance.
Useful when iterating on messaging rather than generating from scratch.
writingStyle
Controls the tone and style of the generated content.
Options include: Professional, Conversational, Punchy, and Custom.
Custom Writing Style
If “Custom” is selected under
writingStyle, users can define their own specific style.Enables unique brand voice alignment by specifying tone preferences.
valueProposition
Allows users to insert a custom value prop for Autobound to weave into the messaging.
Helps tailor outreach to different personas or industries.
salesAsset
Lets users reference a specific sales asset (e.g., case study, whitepaper, blog post).
Ideal for directing prospects to supporting materials within the outreach message.
additionalContext
Enables users to pass in extra details for Autobound to consider when generating content.
Useful for specifying campaign goals, competitive differentiators, or specific call-to-actions.
3. Mapping Autobound’s Content in Clay for Export
Once Autobound generates personalized content, users can map the output fields to custom variables in various outreach platforms:
Email Sequences → Instantly, Smartlead (subject lines & body text as mapped fields).
LinkedIn Messaging → Dripify, Buzz.
CRM & Tracking → Google Sheets, Salesforce, HubSpot.
Here's an example of how we configure it Instantly.
4. Keeping HTML Formatting for Export
Autobound’s content remains in HTML format to preserve paragraph breaks and structure when exported.
Most outbound platforms treat input fields as plain text, so keeping the HTML intact ensures proper formatting.
Get Started with a Clay Table Template
To accelerate setup, use one of the pre-built templates below:
Sequence Table - Ideal for multi-step outreach sequences.
Single Content Item Table - Best for generating a single outbound touchpoint.
By leveraging these templates, users can quickly integrate Autobound’s API into their workflows and start automating hyper-personalized outreach at scale.