Refiner MCP integration for AI agents.
Connect AI agents to Refiner through 12 structured actions, including get account info, add contact to segment, remove contact from segment, and identify use…
- ACTION CONTRACTS
- 12
- 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 Refiner integration exposes
The Refiner Agent App exposes 12 provider-backed actions for marketing and data work. Its current contract lets an authorized agent retrieve the current refiner account, project, and subscription information, add a refiner contact to a manual segment, and remove a refiner contact from a manual segment. 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 Refiner account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Refiner capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_account_infoREADRetrieve the current Refiner account, project, and subscription information.
add_contact_to_segmentWRITEAdd a Refiner contact to a manual segment.
INPUTS: segmentUuid / id / email / uuid
remove_contact_from_segmentHIGH IMPACTRemove a Refiner contact from a manual segment.
INPUTS: segmentUuid / id / email / uuid
identify_userREVIEWCreate or update a Refiner contact using the official identify-user endpoint.
INPUTS: id / email / uuid / name / traits
get_contactREADRetrieve a single Refiner contact by id, email, or uuid.
INPUTS: id / email / uuid
get_reportingREADRetrieve Refiner reporting metrics for forms, segments, and questions.
INPUTS: reportType / questionIdentifiers / formUuids / segmentUuids / tagUuids
list_contactsREADList contacts available in the connected Refiner workspace.
INPUTS: page / pageCursor / pageLength
list_formsREADList forms in the connected Refiner workspace.
INPUTS: uuid / type / currentPage / pageLength / showConfig
list_responsesREADList survey responses collected in Refiner.
INPUTS: currentPage / pageCursor / pageLength / status / formUuid
list_segmentsREADList segments in the connected Refiner workspace.
INPUTS: uuid / currentPage / pageLength
tag_responseREVIEWApply a tag to a Refiner response.
INPUTS: responseUuid / tagName
track_eventREVIEWTrack a product event for a Refiner contact.
INPUTS: id / email / uuid / eventName / sessionId
INPUT CONTRACTS
Know what the action needs before it runs.
add_contact_to_segment
segmentUuidREQUIRED- Segment UUID used for the sync operation.
idOPTIONAL- External user identifier stored in Refiner as id.
emailOPTIONAL- Email address used to identify the Refiner contact.
uuidOPTIONAL- Refiner UUID.
remove_contact_from_segment
segmentUuidREQUIRED- Segment UUID used for the sync operation.
idOPTIONAL- External user identifier stored in Refiner as id.
emailOPTIONAL- Email address used to identify the Refiner contact.
uuidOPTIONAL- Refiner UUID.
identify_user
idOPTIONAL- External user identifier stored in Refiner as id.
emailOPTIONAL- Email address used to identify the Refiner contact.
uuidOPTIONAL- Refiner UUID.
nameOPTIONAL- Display name of the contact.
traitsOPTIONAL- A record of arbitrary values.
get_contact
idOPTIONAL- External user identifier stored in Refiner as id.
emailOPTIONAL- Email address used to identify the Refiner contact.
uuidOPTIONAL- Refiner UUID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account Info
Retrieve the current Refiner account, project, and subscription information. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_account_infoControl Add Contact To Segment
Add a Refiner contact to a manual segment. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_contact_to_segmentVerify with Get Contact
Retrieve a single Refiner contact by id, email, or uuid. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_contactSAFETY BOUNDARY
Operate Refiner with explicit limits
- Authorize Refiner with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `remove_contact_from_segment` 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 Refiner rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Refiner task completed successfully.
CONNECTION MODEL
API key
Refiner API key used with the Authorization Bearer header. Find it in Refiner under Integrations > Rest API: https://refiner.io/docs/api/
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
- 7
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 3
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 Refiner.