Altiria MCP integration for AI agents.
Connect AI agents to Altiria through 8 structured actions, including get contact, create contact, and delete contact. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 8
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Altiria integration exposes
The Altiria Agent App exposes 8 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent fetch one altiria contact by contact id, create a new altiria contact, and delete one altiria 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 Custom credentials. 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 Altiria account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Altiria capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contactREADFetch one Altiria contact by contact ID.
INPUTS: id / include
create_contactWRITECreate a new Altiria contact.
INPUTS: email / phone / landline / countryIso / groupsIds
delete_contactHIGH IMPACTDelete one Altiria contact by contact ID.
INPUTS: id
get_smsREADFetch SMS information from Altiria by one or more message identifiers.
INPUTS: id
list_contactsREADList contacts from the connected Altiria account.
INPUTS: limit / page / include
list_groupsREADList contact groups from the connected Altiria account.
INPUTS: limit / page
send_smsWRITESend an SMS message through Altiria's REST SMS endpoint.
INPUTS: to / from / message / notificationUrl / campaignName
update_contactWRITEUpdate an existing Altiria contact.
INPUTS: id / email / phone / landline / countryIso
INPUT CONTRACTS
Know what the action needs before it runs.
get_contact
idREQUIRED- Altiria contact identifier.
includeOPTIONAL- Associated contact resources to include in the response.
create_contact
emailOPTIONAL- Contact email address.
phoneOPTIONAL- Contact mobile phone number with international prefix.
landlineOPTIONAL- Contact landline phone number.
countryIsoOPTIONAL- Two-letter country code required when phone or landline is specified.
groupsIdsOPTIONAL- Contact group IDs to attach this contact to.
delete_contact
idREQUIRED- Altiria contact identifier.
get_sms
idREQUIRED- Altiria SMS message identifier, or multiple identifiers separated by commas.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Contact
Fetch one Altiria contact by contact ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_contactControl Create Contact
Create a new Altiria contact. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Sms
Fetch SMS information from Altiria by one or more message identifiers. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_smsSAFETY BOUNDARY
Operate Altiria with explicit limits
- Authorize Altiria with Custom credentials and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_contact` 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 Altiria rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Altiria task completed successfully.
CONNECTION MODEL
Custom credentials
Altiria uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
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
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
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 Altiria.