Sales Enablement

Autobound
API integration

Ship Sales Enablement features without building the integration. Full Autobound API access via Proxy and 30+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Talk to us

Use Cases

Why integrate with Autobound

Common scenarios for SaaS companies building Autobound integrations for their customers.

Embed AI-powered signal intelligence in sales tools

Sales engagement platforms can offer their users instant access to 700+ buying signals across 50M+ companies without building data pipelines from scratch. Truto handles the auth and API plumbing so your users connect their Autobound account in a few clicks.

Power autonomous SDR agents with real-time intent

AI-native outbound platforms can subscribe to Autobound webhooks and trigger automated outreach the moment a target account exhibits intent signals like funding events or executive hires. This turns your agent product into a fully event-driven system without managing signal infrastructure.

Enrich and route inbound leads in RevOps platforms

RevOps and lead routing tools can bulk-enrich inbound domains with Autobound signal data to dynamically score and assign leads to the right reps. This adds a high-value enrichment layer to your platform without sourcing buying intent data yourself.

Generate hyper-personalized outreach inside your editor

CRMs and email tools can white-label Autobound's content generation API as an in-product 'auto-draft' feature for emails, call scripts, and LinkedIn openers. Your users get AI copy grounded in real signals, surfaced natively where they already work.

What You Can Build

Ship these features with Truto + Autobound

Concrete product features your team can ship faster by leveraging Truto’s Autobound integration instead of building from scratch.

One-click signal-aware email drafting

Add a button in your email composer that calls Autobound's personalized content API to generate messages referencing real-time buying signals about the recipient.

Chronological account intent timeline

Render a per-company activity feed using Autobound company timelines, showing signals like hiring spikes, funding rounds, and SEC mentions inside your account view.

Webhook-driven sequence enrollment

Let users subscribe to specific Autobound signal types and automatically enroll matching contacts into outbound sequences when those signals fire.

Bulk lead list enrichment

Allow users to upload or sync up to 100 company domains at a time and append signal summaries and scores to each record in your platform.

In-app buyer intent export workflow

Let users define topic lists, kick off async buyer intent exports, and download scored prospect lists directly inside your product without leaving.

Credit usage dashboard and guardrails

Surface remaining Autobound credits and enforce UI-level limits before users trigger high-cost actions like buyer intent exports or sequence generation.

SuperAI

Autobound AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

get_single_autobound_account_by_id

Get the authenticated Autobound account's details. Returns: id and account-specific attributes; the full field breakdown depends on the account's configuration — consult the Autobound API docs for the field-level schema.

get_single_autobound_credit_by_id

Get the current running credit balance for the Autobound workspace. Returns: balance, used, granted, and since. This endpoint is free and consumes no credits.

get_single_autobound_company_by_id

Enrich a single company in Autobound with signal data via POST /v1/companies/enrich. Returns enriched company signal data; the specific request body and response fields are not enumerated in the available source documentation for this endpoint — consult the Autobound API docs for the full schema.

autobound_companies_bulk_create

Bulk-enrich companies in Autobound with signal data via POST /v1/companies/bulk. Returns bulk enrichment results; the specific request body and response fields are not enumerated in the available source documentation for this endpoint — consult the Autobound API docs for the full schema.

create_a_autobound_company

Enrich a company in Autobound with signal data via POST /v1/companies/enrich. Returns enriched company signal data; the specific request body and response fields are not enumerated in the available source documentation for this endpoint — consult the Autobound API docs for the full schema.

list_all_autobound_companies

Search Autobound companies by signal type to discover distinct companies that have one or more matching signals, sorted by most-recent signal. Returns: domain, name, linkedin_url, signal_count, most_recent_signal_at, signals. Required: signal_types. Entity filters (industries, employee_count_min/max, seniority, department, job_title) cap the detectable window to the most recent 14 days. Costs 2 credits per company returned.

get_single_autobound_company_timeline_by_id

Get the Twitter/X timeline data for a company in Autobound. Returns engagement metrics, account metadata, and AI-enriched fields including num_likes, num_reposts, company_twitter_handle, company_twitter_followers, summary, tags, pain_points, and initiatives. Required: id.

create_a_autobound_contact

Enrich a contact in Autobound with B2B buying signals by email or LinkedIn URL. Returns `contact`, `company`, `contact_signals`, `signal_summary`, `total`, and `coverage`. Provide at least one of `contact_email` or `contact_linkedin_url`. Costs 2 credits per signal returned.

autobound_contacts_bulk_create

Look up shared experiences between sellers and a contact in Autobound. Returns `contactEmail`, `contactLinkedinUrl`, `companyUrl`, `companyLinkedinUrl`, and a `data` array of shared experience objects covering company overlap, city overlap, and school overlap.

list_all_autobound_contacts

Search Autobound contacts that have matching B2B buying signals, sorted by most-recent signal. Returns one record per contact including `email`, `name`, `title`, `company`, `signal_count`, `most_recent_signal_at`, and `signals`. Costs 2 credits per contact returned. Applying entity filters (`industries`, `seniority`, `department`, `job_title`, `employee_count_min`, `employee_count_max`) caps the search window to the most recent 14 days.

list_all_autobound_contact_timelines

List contact timeline events in Autobound, returning shared experiences between your team members and a contact. Returns: contactEmail, contactLinkedinUrl, companyUrl, companyLinkedinUrl, and a data array of shared-experience objects each containing subtype, userLinkedinUrl, contactLinkedinUrl, userName, contactName, and experience-specific fields.

get_single_autobound_signal_by_id

Get a single Autobound signal by its id. Returns: signal_id, signal_type, signal_subtype, signal_name, detected_at, association, company, contact, and data. Required: id. This endpoint has no credit cost.

list_all_autobound_signals

List trending Autobound signals from the real-time B2B signal feed. Returns: signal_id, signal_type, signal_subtype, signal_name, detected_at, association, company, contact, and data per signal.

autobound_signals_search

Search Autobound signals using structured filters. Returns matching signal records including signal_id, signal_type, signal_subtype, signal_name, detected_at, association, company, contact, and data.

list_all_autobound_signal_types

List all signal types in Autobound — the canonical catalog of type slugs accepted as filter values by other endpoints. Returns: type, association, description, count, refresh_cadence, refresh_hours. Pass include_counts=true to receive per-type row counts and metadata alongside each slug.

get_single_autobound_signal_type_by_id

Get detection-date histogram data for a single Autobound signal type. Returns: type, interval, history (array of period/count buckets), total. Required: id. Accepts both canonical slugs (e.g. sec-8k) and legacy aliases (e.g. 8k).

list_all_autobound_webhooks

List Autobound webhooks configured for real-time push delivery of intent signals. Returns: id.

create_a_autobound_webhook

Create an Autobound webhook to enable real-time push delivery of intent signals to your endpoint. Returns: id.

update_a_autobound_webhook_by_id

Update an Autobound webhook configuration by id. Returns: id. Required: id.

delete_a_autobound_webhook_by_id

Delete an Autobound webhook by id. Returns an empty 204 response on success. Required: id.

create_a_autobound_buyer_intent_export

Submit an async bulk buyer-intent export job in Autobound. Returns: export_id and status. Required: topic_ids. Supports up to 1,000 topic IDs per job; costs 10 credits per topic. Use the returned export_id to poll job status via the get method.

get_single_autobound_buyer_intent_export_by_id

Poll the status of a buyer-intent export job in Autobound by id. Returns: export_id, status, and download_url (populated when the job is ready for download). Required: id.

create_a_autobound_personalized_content

Generate hyper-personalized outreach content in Autobound across formats such as email, sequence, call script, connection request, SMS, opener, or custom. Returns generated content items including subject, content body, modelUsed, and insightsUsed. Required: contentType, plus either contactEmail or contactLinkedinUrl, and either userEmail or userLinkedinUrl. When contentType is 'sequence', each email consumes 2 credits; n is not compatible with 'sequence'.

list_all_autobound_credit_costs

List the per-action credit cost table for your Autobound workspace. Returns: action, cost, description, chargeMode for each pricing row, plus optional floor and base fields when applicable to your workspace's pricing schedule.

list_all_autobound_logs

List recent API request logs in Autobound covering the last 30 days (free, no credits consumed). Returns: type, method, path, status, latency_ms, timestamp for each log entry. Filter by endpoint path, HTTP method, status code range, or timestamp window using since/before.

get_single_autobound_stat_by_id

Get Autobound corpus statistics including aggregate signal counts broken down by type. Returns: total_signals, total_types, signal_types (array of per-type slug/count pairs), and last_detected_at. No required parameters; this endpoint is free and consumes no credits.

get_single_autobound_health_by_id

Get the overall service health of Autobound. Returns: status, timestamp, version, services, and uptime. No authentication required.

list_all_autobound_buyer_intent_topics

List Autobound buyer-intent topics from a catalog of ~38K entries. Supports fuzzy search via q and filtering by category, sub_category, or is_product. Returns: topic_id, category, subcategory, topic, description, is_product. No credit cost.

get_single_autobound_buyer_intent_filter_by_id

Get the valid filter enum values for buyer-intent contact searches in Autobound. Returns: seniority, department, revenue_buckets, size_buckets, country, and categories (intent topic categories with subcategories and topic counts). No required parameters; this endpoint is free and does not consume credits.

list_all_autobound_buyer_intent_companies

List Autobound companies surging on specified buyer-intent topics, drawn from the weekly pre-scored intent snapshot and ranked by composite intent score. Returns: topic_id, intent_score, stage_label, signal_week, topic (name, category, subcategory, is_product), and company. Required: topic_ids (1–10 topic IDs). Credit cost: 1 per company-topic row returned.

autobound_buyer_intent_companies_bulk_create

Submit an asynchronous bulk export of company intent rows for up to 1,000 topics in Autobound. The job is queued immediately and streams results as JSONL to cloud storage. Returns: export_id (cexp_-prefixed), status, credits_charged, topics, credits_per_topic, base, and created_at. Poll GET /v1/buyer-intent/exports/{exportId} with the returned export_id for download. Required: topic_ids.

list_all_autobound_buyer_intent_contacts

List Autobound contacts showing buyer intent for one or more topics. Returns each contact's topic_id, intent_score, contact details (email, job_title, linkedin_url, opted_out), company firmographics (name, domain, industry, revenue), and filters (seniority, department). Required: topic_ids. Costs 1 credit per contact returned; max 250 per page.

create_a_autobound_buyer_intent_contact_export

Submit an asynchronous bulk contact intent export job in Autobound. Returns immediately with HTTP 202 including export_id, status, credits_charged, topics, credits_per_topic, base, and created_at; poll GET /v1/buyer-intent/exports/{exportId} until status is `ready` (24-hour signed download URL) or `failed`. Required: topic_ids. Supports up to 1,000 topic IDs and up to 10,000,000 exported rows.

get_single_autobound_company_intent_timeline_by_id

Get the intent-score timeline for a single company in Autobound across all buyer-intent topics, drawn from the weekly snapshot. Returns: company (domain, name, industry, employee_count, linkedin_url), timeline (array of per-topic entries with topic_id, composite_score, stage_label, signal_week), and count. An unknown domain returns 200 with an empty timeline and null firmographics. Required: id (company domain, max 253 chars). Credit cost: free.

autobound_monitoring_pool_records_bulk_create

Add 1–100 companies or contacts to the Autobound signal monitoring pool in a single batch. Returns per-record results including index, status, and id (pool entry UUID for accepted records). Required: records. All-or-nothing validation — if any record fails, the entire batch is rejected and nothing is added. Costs 10 credits per net-new record; duplicates are free.

Why Truto

Why use Truto’s MCP server for Autobound

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 500+ integrations.

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Go live with Autobound in under an hour. No boilerplate, no maintenance burden.

Link your customer’s Autobound account

Use Truto’s frontend SDK to connect your customer’s Autobound account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

Call our API, we call Autobound

Truto’s Proxy API is a 1-to-1 mapping of the Autobound API. You call us, we call Autobound, and pass the response back in the same cycle.

Unified response format

Every response follows a single format across all integrations. We translate Autobound’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Autobound on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How does authentication work for connecting end-user Autobound accounts?

Truto handles the Autobound API key exchange and stores credentials securely per end-user. Your users connect their Autobound account once through Truto's connect flow, and you call Autobound APIs against that connection without managing keys yourself.

Can we receive real-time signal notifications instead of polling?

Yes. You can use the webhook tools to programmatically register callback URLs per user and subscribe to specific signal types from Autobound's catalog. Truto normalizes webhook delivery so you receive events at a single endpoint regardless of which user's connection fired them.

How do we handle the async nature of buyer intent exports?

Create an export job with create_a_autobound_buyer_intent_export, then poll get_single_autobound_buyer_intent_export_by_id until the status is ready. Autobound returns a download URL valid for 24 hours pointing to a JSONL file of intent-scored contacts.

What are the bulk operation limits?

Autobound supports up to 100 domains per bulk company create call and up to 1,000 topic IDs per buyer intent export job. You should batch requests in your platform accordingly when enriching large lead lists.

How do we manage Autobound's credit-based pricing per user?

Use get_single_autobound_account_by_id and get_single_autobound_credit_by_id to read remaining credits and limits for each connected user. This lets you display usage in your UI and block actions before they fail, since operations like buyer intent (10 credits per topic) and sequences (2 credits per email) consume credits at different rates.

Can we generate different content formats beyond email?

Yes. create_a_autobound_personalized_content supports multiple content types including emails, sequences, SMS, call scripts, and LinkedIn openers. The response includes metadata about which signals informed the generated copy so you can surface attribution in your UI.

From the Blog

Autobound integration guides

Deep dives, architecture guides, and practical tutorials for building Autobound integrations.

Autobound

Get Autobound integrated into your app

Our team understands what it takes to make a Autobound integration successful. A short, crisp 30 minute call with folks who understand the problem.