BetterContact MCP integration for AI agents.
Connect AI agents to BetterContact through 3 structured actions, including get account balance, submit enrichment, and get enrichment result. Review authenti…
- ACTION CONTRACTS
- 3
- 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 BetterContact integration exposes
The BetterContact Agent App exposes 3 provider-backed actions for marketing and data work. Its current contract lets an authorized agent get bettercontact credits for the connected account email or an optional email override, submit one or more leads to bettercontact waterfall enrichment and return the request handle, and get the current bettercontact enrichment result for a submitted request id. 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 BetterContact account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BetterContact capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_account_balanceREADGet BetterContact credits for the connected account email or an optional email override.
INPUTS: email
submit_enrichmentREVIEWSubmit one or more leads to BetterContact waterfall enrichment and return the request handle.
INPUTS: leads / enrichEmailAddress / enrichPhoneNumber / webhookUrl / processFlowId
get_enrichment_resultREADGet the current BetterContact enrichment result for a submitted request ID.
INPUTS: requestId
INPUT CONTRACTS
Know what the action needs before it runs.
get_account_balance
emailOPTIONAL- Optional BetterContact account email to query instead of the email stored during connection.
submit_enrichment
leadsREQUIRED- The leads to enrich. BetterContact supports up to 100 leads per request.
enrichEmailAddressREQUIRED- Whether BetterContact should enrich work email addresses for the submitted leads.
enrichPhoneNumberREQUIRED- Whether BetterContact should enrich direct phone numbers for the submitted leads.
webhookUrlOPTIONAL- Optional webhook URL where BetterContact should push the enrichment result.
processFlowIdOPTIONAL- Optional BetterContact process flow ID when your account uses the process flow add-on.
get_enrichment_result
requestIdREQUIRED- The BetterContact request ID returned by submit_enrichment.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account Balance
Get BetterContact credits for the connected account email or an optional email override. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_account_balanceVerify with Get Enrichment Result
Get the current BetterContact enrichment result for a submitted request ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_enrichment_resultSAFETY BOUNDARY
Operate BetterContact with explicit limits
- Authorize BetterContact with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BetterContact 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 BetterContact rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BetterContact task completed successfully.
CONNECTION MODEL
API key
BetterContact API key used with the X-API-Key header. Find it in the BetterContact API Requests page: https://app.bettercontact.rocks/api_requests.
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
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 BetterContact.