Sales Enablement · Beta

Autobound
API integration

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

Built for specific customer use cases. Issues are resolved quickly.

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 Autobound account information including rate limits and credit usage. Returns: customer_id, customer_name, rate_limit, and credits (monthly_limit, used, remaining, period_reset).

get_single_autobound_credit_by_id

Get the current credit balance and usage for an Autobound account. Returns: monthly_limit, used, remaining, period_start, period_reset, and unlimited. This call does not consume credits.

get_single_autobound_company_by_id

Enrich a single company in Autobound with signal intelligence. Returns the company profile (name, domain, industries), an array of detected signals (signal_type, detected_at, score), and a signal_summary. Supply at least one of domain, company_name, or linkedin_url.

autobound_companies_bulk_create

Bulk enrich up to 100 companies in Autobound with signal intelligence in a single request. Returns total_companies processed and a results array containing the company profile, signals, and signal_summary for each domain. Required: domains.

get_single_autobound_company_timeline_by_id

Get a chronological timeline of buying signals for a specific company in Autobound. Returns: timeline (array of signals with signal_id, signal_type, detected_at), total, and has_more. Required: id (company domain).

create_a_autobound_contact

Enrich a single contact in Autobound with signal intelligence by supplying an email or LinkedIn URL. Returns the contact profile, company information, contact_signals, and signal_summary. Provide at least contact_email or contact_linkedin_url.

autobound_contacts_bulk_create

Bulk enrich up to 100 contacts in Autobound with signal intelligence in a single request. Returns total_contacts and a results array with per-contact profile, company information, contact_signals, and signal_summary. Required: contacts.

list_all_autobound_contact_timelines

List contact timeline events in Autobound. Returns a collection of timeline entries associated with contacts.

get_single_autobound_signal_by_id

Get a single Autobound signal by id. Returns: signal_id, signal_type, detected_at, association, score, and associated company and contact details. Required: id.

list_all_autobound_signals

List trending Autobound signals within a specified time window. Returns: an array of signals each with signal_id, signal_type, detected_at, and score, plus a total count and signal_summary aggregate breakdown.

autobound_signals_search

Search Autobound signals by posting a query. Returns matching signals from the Autobound signals index.

list_all_autobound_signal_types

List all available signal types in Autobound. Returns: type, association, description, and optionally count per type, plus total_signals across all types.

list_all_autobound_webhooks

List all active Autobound webhook subscriptions for your account. Returns an array of webhook objects including webhook_id, url, signal_types, and created_at.

create_a_autobound_webhook

Create a new Autobound webhook subscription to receive real-time signal notifications at a specified URL. Returns the created webhook including webhook_id, url, signal_types, and created_at. Required: url.

update_a_autobound_webhook_by_id

Update an existing Autobound webhook subscription's URL, signal types, or description by id. Returns the updated webhook object including webhook_id, url, signal_types, and updated_at. Required: id.

delete_a_autobound_webhook_by_id

Permanently delete an Autobound webhook subscription by id. Returns an empty 204 response on success. Required: id.

create_a_autobound_buyer_intent_export

Submit an async buyer intent export job in Autobound to generate a downloadable JSONL file of intent contacts. Returns: export_id, status, created_at. Required: topic_ids. Supports up to 1,000 topics per request; costs 10 credits per topic submitted.

get_single_autobound_buyer_intent_export_by_id

Poll the status of an Autobound buyer intent export job by id. Returns: export_id, status, and when ready, download_url, total_contacts, topics_queried, and expires_at. Required: id. Download URLs expire after 24 hours.

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'.

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.