Manatal MCP integration for AI agents.
Connect AI agents to Manatal through 16 structured actions, including get candidate, create candidate, and create job. Review authentication, inputs, workflo…
- ACTION CONTRACTS
- 16
- 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 Manatal integration exposes
The Manatal Agent App exposes 16 provider-backed actions for productivity work. Its current contract lets an authorized agent retrieve a single manatal candidate by id, create a manatal candidate using json-safe profile fields, and create a manatal job using json-safe job fields. 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 Manatal account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Manatal capabilities.
Showing 12 of 16 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_candidateREADRetrieve a single Manatal candidate by ID.
INPUTS: candidateId
create_candidateWRITECreate a Manatal candidate using JSON-safe profile fields.
INPUTS: fullName / externalId / owner / sourceType / sourceOther
create_jobWRITECreate a Manatal job using JSON-safe job fields.
INPUTS: organization / positionName / externalId / description / expectedCloseAt
create_matchWRITECreate a Manatal candidate-job match using JSON-safe match fields.
INPUTS: job / candidate / owner / externalId / isActive
create_organizationWRITECreate a Manatal organization using JSON-safe organization fields.
INPUTS: name / externalId / owner / address / website
get_jobREADRetrieve a single Manatal job by ID.
INPUTS: jobId
get_matchREADRetrieve a single Manatal candidate-job match by ID.
INPUTS: matchId
get_organizationREADRetrieve a single Manatal organization by ID.
INPUTS: organizationId
list_candidatesREADList Manatal candidates with pagination and recruitment profile filters.
INPUTS: page / pageSize / id / fullName / creatorId
list_jobsREADList Manatal jobs with pagination and job status filters.
INPUTS: page / pageSize / id / organizationId / positionName
list_matchesREADList Manatal candidate-job matches with pagination and pipeline filters.
INPUTS: page / pageSize / ordering / externalId / stageIn
list_organizationsREADList Manatal organizations with pagination and organization filters.
INPUTS: page / pageSize / id / name / creatorId
INPUT CONTRACTS
Know what the action needs before it runs.
get_candidate
candidateIdOPTIONAL- ID of the Manatal candidate to retrieve.
create_candidate
fullNameREQUIRED- Full name of the candidate.
externalIdOPTIONAL- ID of the candidate in an external system.
ownerOPTIONAL- ID of the owner of the candidate.
sourceTypeOPTIONAL- Origin of the candidate.
sourceOtherOPTIONAL- Manual source information when sourceType is other.
create_job
organizationREQUIRED- ID of the organization the job is assigned to.
positionNameREQUIRED- Job title.
externalIdOPTIONAL- ID of the job in an external system.
descriptionOPTIONAL- Description of the job.
expectedCloseAtOPTIONAL- Expected date and time when the job will be closed or filled.
create_match
jobREQUIRED- ID of the job the candidate is matched with.
candidateREQUIRED- ID of the candidate matched to the job.
ownerOPTIONAL- ID of the owner of the match.
externalIdOPTIONAL- ID of the match in an external system.
isActiveOPTIONAL- Whether the match is still active.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Candidate
Retrieve a single Manatal candidate 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_candidateControl Create Candidate
Create a Manatal candidate using JSON-safe profile fields. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_candidateVerify with Get Job
Retrieve a single Manatal job by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_jobSAFETY BOUNDARY
Operate Manatal with explicit limits
- Authorize Manatal with API key and grant only the provider access required by the selected actions.
- 8 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- 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 Manatal rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Manatal task completed successfully.
CONNECTION MODEL
API key
Manatal API token used with the Authorization: Token <apiKey> header. Manatal says Open API tokens are obtained from its support team: https://developers.manatal.com/reference/getting-started.
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
- 8
- WRITE SIGNALS
- 8
- HIGH IMPACT
- 0
- 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 Manatal.