SureContact MCP integration for AI agents.
Connect AI agents to SureContact through 23 structured actions, including add contacts to list, create contact, delete contact, and attach contact lists. Rev…
- ACTION CONTRACTS
- 23
- 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 SureContact integration exposes
The SureContact Agent App exposes 23 provider-backed actions for marketing and productivity work. Its current contract lets an authorized agent add one or more surecontact contacts to a list, create a surecontact contact and optionally attach lists or tags, and delete a surecontact contact by uuid. 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 SureContact account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real SureContact capabilities.
Showing 12 of 23 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
add_contacts_to_listREADAdd one or more SureContact contacts to a list.
INPUTS: listUuid / contactUuids
create_contactWRITECreate a SureContact contact and optionally attach lists or tags.
INPUTS: email / firstName / lastName / phone / status
delete_contactHIGH IMPACTDelete a SureContact contact by UUID.
INPUTS: uuid
attach_contact_listsREVIEWAttach one or more SureContact lists to a contact.
INPUTS: contactUuid / uuids
attach_contact_tagsREVIEWAttach one or more SureContact tags to a contact.
INPUTS: contactUuid / uuids
create_listREADCreate a SureContact list.
INPUTS: name / description
create_tagWRITECreate a SureContact tag.
INPUTS: name
delete_listHIGH IMPACTDelete a SureContact list by UUID.
INPUTS: uuid
delete_tagHIGH IMPACTDelete a SureContact tag by UUID.
INPUTS: uuid
detach_contact_listsREVIEWDetach one or more SureContact lists from a contact.
INPUTS: contactUuid / uuids
detach_contact_tagsREVIEWDetach one or more SureContact tags from a contact.
INPUTS: contactUuid / uuids
get_contactREADRetrieve one SureContact contact by UUID.
INPUTS: uuid
INPUT CONTRACTS
Know what the action needs before it runs.
add_contacts_to_list
listUuidOPTIONAL- The SureContact list UUID.
contactUuidsOPTIONAL- SureContact contact UUIDs to add or remove.
create_contact
emailREQUIRED- Contact email address.
firstNameOPTIONAL- Contact first name.
lastNameOPTIONAL- Contact last name.
phoneOPTIONAL- Contact phone number.
statusOPTIONAL- Contact subscription status.
delete_contact
uuidOPTIONAL- The SureContact contact UUID.
attach_contact_lists
contactUuidOPTIONAL- The SureContact contact UUID.
uuidsOPTIONAL- SureContact resource UUIDs to attach.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Add Contacts To List
Add one or more SureContact contacts to a list. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
add_contacts_to_listControl Create Contact
Create a SureContact contact and optionally attach lists or tags. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Create List
Create a SureContact list. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_listSAFETY BOUNDARY
Operate SureContact with explicit limits
- Authorize SureContact with API key and grant only the provider access required by the selected actions.
- 9 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_contact`, `delete_list`, and `delete_tag` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in SureContact rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the SureContact task completed successfully.
CONNECTION MODEL
API key
SureContact API key sent with the X-API-Key header. Create or view it from the SureContact API settings area documented at https://api.surecontact.com/docs.
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
- 10
- WRITE SIGNALS
- 5
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 4
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 SureContact.