Certn MCP integration for AI agents.
Connect AI agents to Certn through 10 structured actions, including get case, get group, and get user. Review authentication, inputs, workflows, and safety g…
- ACTION CONTRACTS
- 10
- 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 Certn integration exposes
The Certn Agent App exposes 10 provider-backed actions for security and productivity work. Its current contract lets an authorized agent retrieve one certn background-check case by uuid, retrieve one certn group by uuid, and retrieve one certn client portal user 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 Certn account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Certn capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_caseREADRetrieve one Certn background-check case by UUID.
INPUTS: id
get_groupREADRetrieve one Certn group by UUID.
INPUTS: id
get_userREADRetrieve one Certn Client Portal user by UUID.
INPUTS: id
list_casesREADList Certn background-check cases with pagination and optional filters.
INPUTS: page / pageSize / emailAddress / groupIds / overallStatuses
list_eventsREADList historical Certn events with optional incremental cursor filtering.
INPUTS: page / lastProcessedEventId
list_groupsREADList Certn groups with pagination and optional filters.
INPUTS: page / pageSize / id / isActive / name
list_packagesREADList Certn check packages with pagination and optional filters.
INPUTS: page / pageSize / isActive / permissiblePurposes
list_questionnairesREADList Certn questionnaire templates with pagination.
INPUTS: page / pageSize
list_tagsREADList Certn tags with pagination and optional ID filtering.
INPUTS: page / pageSize / id / isActive / name
list_usersREADList Certn Client Portal users with pagination and optional filters.
INPUTS: page / pageSize / email / fullName / groupIds
INPUT CONTRACTS
Know what the action needs before it runs.
get_case
idOPTIONAL- Certn UUID.
get_group
idOPTIONAL- Certn UUID.
get_user
idOPTIONAL- Certn UUID.
list_cases
pageOPTIONAL- One-based page number to request from Certn.
pageSizeOPTIONAL- Number of results to return per page. Certn defaults to 10 and allows at most 100.
emailAddressOPTIONAL- Filter cases by applicant email address.
groupIdsOPTIONAL- Filter cases by one or more Certn group UUIDs.
overallStatusesOPTIONAL- Filter cases by one or more Certn overall status values.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Case
Retrieve one Certn background-check case by UUID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_caseVerify with Get Group
Retrieve one Certn group by UUID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_groupSAFETY BOUNDARY
Operate Certn with explicit limits
- Authorize Certn with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Certn 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 Certn rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Certn task completed successfully.
CONNECTION MODEL
API key
Certn API key sent as Authorization: Api-Key. Create and manage API keys in the Client Portal under Settings > Integrations > API Keys, as documented at https://centric-api-docs.certn.co/#authentication.
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
- 0
- 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 Certn.