Supported HTTP methods
Autobound supports:
• GET
• POST
• PUT
• PATCH
Where to find Export via API
In AI Studio:
Open a table
Click Action → Export or Send → Export via API
Step 1: Create an Export
Name your export
Enter your API endpoint URL
Select the HTTP method
Set up Query parameters, Headers, Body, retry settings (auto-retry is on by default), and conditional run settings.
Step 2: API endpoint URL
Enter the full URL where the request should be sent.
You can reference table columns dynamically in the URL by typing / and selecting the column you want to reference. This is useful when the endpoint requires row-specific data, such as a contact or record ID.
Example:
Step 3: HTTP method
Choose the method your endpoint expects:
• GET
• POST
• PUT
• PATCH
Step 4: JSON body
For GET, POST, PUT, and PATCH requests, specify the data to send in the request body.
Important JSON formatting rules
• String values need quotes
• Numbers and booleans do not
• Dynamic column references for strings need quotes
• Dynamic column references for numbers do not
• Numbers with leading zeros should be wrapped in quotes
Example body configuration
{
"firstName": "{{First Name}}",
"lastName": "{{Last Name}}",
"email": "{{Email}}",
"score": {{Lead Score}},
"subscribed": true
} |
All values are optional.
Empty values will not break the request.
Common mistakes
Wrong:
{ "name": {{Name}} }
Correct:
{ "name": "{{Name}}" }
Wrong:
{ "name": "John" "age": 30 }
Correct:
{ "name": "John", "age": 30 }
Step 5: Headers
Add any headers required by your API.
Common headers:
• Authorization
• API keys
• Content-Type
Content-Type is not automatically set and should be added if required.
Header values can reference table columns. This is useful when authentication or routing depends on row-level data.
Example:
{
"Authorization": "Bearer {{API Token}}",
"Content-Type": "application/json"
} |
Step 6: Conditional runs
You can control when the export runs using conditions.
Examples:
• Only run when AI content exists
• Only run when a status column equals a value
• Only run after enrichment completes
This prevents unnecessary API calls.
Step 7: Run behavior
Exports support multiple execution modes.
Manual run:
• Trigger the export on a specific row
Automatic run:
• Runs when a row is created or updated
Conditional automatic run:
• Runs only when conditions are met
Retries and rate limiting
Autobound automatically handles reliability.
• Automatic retry up to 3 times
• Rate limited to 10 requests per second
• No custom rate limit configuration
Failures are isolated to individual rows.
Error handling
If a request fails:
• The row shows an error state
• You can retry after fixing the issue
• Other rows continue processing
Common use cases
• Push AI-written emails into sequencing tools
• Sync research and insights into CRMs
• Trigger internal workflows from AI Studio
• Send enrichment or scoring data to external systems
Formatting notes
For email content:
• Use HTML output to preserve formatting
• Convert to plain text downstream if required
What Autobound does not support
Export via API does not support:
• Importing data from APIs
• Response or result path configuration
• Field extraction from API responses
• Integration templates
• Custom rate limit configuration
• DELETE requests
• Pagination or multi-page API pulls