Amplemarket MCP integration for AI agents.
Connect AI agents to Amplemarket through 11 structured actions, including get account details, complete task, and get contact. Review authentication, inputs…
- ACTION CONTRACTS
- 11
- 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 Amplemarket integration exposes
The Amplemarket Agent App exposes 11 provider-backed actions for marketing and data work. Its current contract lets an authorized agent get account details for the authenticated amplemarket api key, mark an amplemarket task as completed, and retrieve an amplemarket contact by contact 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 Amplemarket account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Amplemarket capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_account_detailsREADGet account details for the authenticated Amplemarket API key.
complete_taskREVIEWMark an Amplemarket task as completed.
INPUTS: id
get_contactREADRetrieve an Amplemarket contact by contact ID.
INPUTS: id
get_contact_by_emailREADRetrieve an Amplemarket contact by email address.
INPUTS: email
get_lead_listREADRetrieve an Amplemarket lead list by ID.
INPUTS: id
list_contactsREADRetrieve Amplemarket contacts by one or more contact IDs.
INPUTS: ids
list_lead_listsREADList Amplemarket lead lists with cursor pagination and owner filters.
INPUTS: page_size / page_after / page_before / status / owner_id
list_task_statusesREADList task statuses supported by Amplemarket.
list_task_typesREADList task types supported by Amplemarket.
list_tasksREADList Amplemarket tasks with cursor pagination and status, type, or user filters.
INPUTS: page_size / page_after / page_before / status / type
skip_taskREVIEWSkip an Amplemarket task.
INPUTS: id
INPUT CONTRACTS
Know what the action needs before it runs.
complete_task
idOPTIONAL- Amplemarket task ID.
get_contact
idOPTIONAL- Amplemarket contact ID.
get_contact_by_email
emailOPTIONAL- Email address of the Amplemarket contact.
get_lead_list
idOPTIONAL- Amplemarket lead list ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account Details
Get account details for the authenticated Amplemarket API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_account_detailsVerify with Get Contact
Retrieve an Amplemarket contact by contact ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_contactSAFETY BOUNDARY
Operate Amplemarket with explicit limits
- Authorize Amplemarket with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Amplemarket 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 Amplemarket rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Amplemarket task completed successfully.
CONNECTION MODEL
API key
Amplemarket API key used as a Bearer token. Create or view it in the Amplemarket Dashboard under Settings > API: https://docs.amplemarket.com/guides/quickstart.
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
- 9
- 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 Amplemarket.