Autobound MCP integration for AI agents.
Connect AI agents to Autobound through 6 structured actions, including get account, enrich company, and enrich contact. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Autobound integration exposes
The Autobound Agent App exposes 6 provider-backed actions for data and marketing work. Its current contract lets an authorized agent get the authenticated autobound signals account details and current credit balance, enrich one company with autobound company-level signals, and enrich one contact with autobound contact-level signals and employer context. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Autobound account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Autobound capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADGet the authenticated Autobound Signals account details and current credit balance.
enrich_companyREVIEWEnrich one company with Autobound company-level signals.
INPUTS: domain / companyName / linkedinUrl / signalTypes / detectedAfter
enrich_contactREVIEWEnrich one contact with Autobound contact-level signals and employer context.
INPUTS: contactEmail / contactLinkedinUrl / signalTypes / detectedAfter / limit
list_signal_typesREADList Autobound signal types and optionally include live counts and refresh cadence metadata.
INPUTS: includeCounts / association / since
search_companiesREADSearch companies that match Autobound company-level signal filters.
INPUTS: signalTypes / signalSubtype / detectedAfter / detectedBefore / limit
search_contactsREADSearch contacts that match Autobound contact-level signal filters.
INPUTS: signalTypes / signalSubtype / detectedAfter / detectedBefore / limit
INPUT CONTRACTS
Know what the action needs before it runs.
enrich_company
domainOPTIONAL- The company domain to enrich, for example stripe.com.
companyNameOPTIONAL- The company name to enrich when the domain is unavailable.
linkedinUrlOPTIONAL- The company LinkedIn URL to enrich when other identifiers are unavailable.
signalTypesOPTIONAL- The signal types Autobound should include in the enrichment response.
detectedAfterOPTIONAL- Only return signals detected on or after this timestamp.
enrich_contact
contactEmailOPTIONAL- The contact email address to enrich.
contactLinkedinUrlOPTIONAL- The contact LinkedIn URL to enrich when the email is unavailable.
signalTypesOPTIONAL- The signal types Autobound should include in the enrichment response.
detectedAfterOPTIONAL- Only return signals detected on or after this timestamp.
limitOPTIONAL- The maximum number of signals to return.
list_signal_types
includeCountsOPTIONAL- Whether Autobound should include per-type counts and cadence metadata.
associationOPTIONAL- The Autobound signal association for filtering or classification.
sinceOPTIONAL- Only include type counts for signals detected on or after this timestamp.
search_companies
signalTypesREQUIRED- The Autobound signal types that companies must match.
signalSubtypeOPTIONAL- The Autobound signal subtype filter.
detectedAfterOPTIONAL- Only include companies with matching signals detected on or after this timestamp.
detectedBeforeOPTIONAL- Only include companies with matching signals detected before this timestamp.
limitOPTIONAL- The maximum number of companies to return.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Get the authenticated Autobound Signals account details and current credit balance. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountVerify with List Signal Types
List Autobound signal types and optionally include live counts and refresh cadence metadata. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_signal_typesSAFETY BOUNDARY
Operate Autobound with explicit limits
- Authorize Autobound with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Autobound data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Autobound rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Autobound task completed successfully.
CONNECTION MODEL
API key
Autobound Signal API key sent with the x-api-key header. Create or copy it from the Signal API dashboard at https://signalapi.autobound.ai.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Autobound.