Agiled MCP integration for AI agents.
Connect AI agents to Agiled through 15 structured actions, including get contact, create contact, and delete contact. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 15
- 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 Agiled integration exposes
The Agiled Agent App exposes 15 provider-backed actions for productivity and data work. Its current contract lets an authorized agent get one agiled crm contact by id, create an agiled crm contact, and delete an agiled crm contact. 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 Agiled account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Agiled capabilities.
Showing 12 of 15 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contactREADGet one Agiled CRM contact by ID.
INPUTS: id
create_contactWRITECreate an Agiled CRM contact.
INPUTS: first_name / last_name / email / role / phone
delete_contactHIGH IMPACTDelete an Agiled CRM contact.
INPUTS: id
create_projectWRITECreate an Agiled project.
INPUTS: project_name / project_summary / start_date / deadline / notes
create_taskWRITECreate an Agiled task.
INPUTS: heading / description / start_date / due_date / user_id
delete_projectHIGH IMPACTDelete an Agiled project.
INPUTS: id
delete_taskHIGH IMPACTDelete an Agiled task.
INPUTS: id
get_projectREADGet one Agiled project by ID.
INPUTS: id
get_taskREADGet one Agiled task by ID.
INPUTS: id
list_contactsREADList Agiled CRM contacts.
list_projectsREADList Agiled projects.
list_tasksREADList Agiled tasks.
INPUT CONTRACTS
Know what the action needs before it runs.
get_contact
idOPTIONAL- Agiled resource ID.
create_contact
first_nameREQUIRED- Contact first name.
last_nameOPTIONAL- Contact last name.
emailOPTIONAL- Contact email address.
roleOPTIONAL- Contact role, such as Client, Lead, or Prospect.
phoneOPTIONAL- Contact phone number.
delete_contact
idOPTIONAL- Agiled resource ID.
create_project
project_nameREQUIRED- Project name.
project_summaryOPTIONAL- Project summary.
start_dateREQUIRED- Project start date using the company's configured date format.
deadlineOPTIONAL- Project deadline using the company's configured date format.
notesOPTIONAL- Project notes.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Contact
Get one Agiled CRM contact by 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 an Agiled CRM contact. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Project
Get one Agiled project by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_projectSAFETY BOUNDARY
Operate Agiled with explicit limits
- Authorize Agiled 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_project`, and `delete_task` 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 Agiled rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Agiled task completed successfully.
CONNECTION MODEL
API key
Agiled API token sent as the api_token query parameter. Create or view it in Settings > API Settings in your Agiled account: https://my.agiled.app/developers.
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
- 6
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 3
- 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 Agiled.