Faster integration delivery
Ship integrations without building each connector from scratch

Build in-app integrations that surface Access CRM enquiries, persons, applicants, clients, jobs and placements inside your product. Use Cyclr to sync records, run incremental pulls, and automate pipeline or marketing workflows for every customer account without custom point-to-point engineering.
Ship integrations without building each connector from scratch
Build workflows once then reuse across customer accounts
Control credentials, approvals and per-account deployment rules
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Teams can integrate and automate Access CRM enquiries, persons/applicants, clients, jobs, placements and incremental updates between Access CRM and their SaaS product. Cyclr provides a low-code builder and connector methods to list, get, incrementally sync and update CRM objects, letting product teams orchestrate multi-tenant workflows and publish them through an embedded marketplace or MCP delivery model.
PRODUCT USE CASES
Quickly build tenant-aware automations that read new web enquiries, sync client and accounting records, automate pipeline updates and push marketing opt-ins to Mailchimp or Klaviyo. Publish these as self-serve integrations in your embedded marketplace or install them per account.
Use Access CRM web enquiry and applicant methods to pull new enquiries and match them to in-app customer records for faster lead follow-up.
Automate client record reconciliation with Access Financials by mapping clients and custom client fields for accurate billing and reporting.
Keep pipeline stages in sync by running List Updated Jobs or List Updated Placements to update opportunity status and trigger downstream workflows.
ORCHESTRATION
Cyclr sits between your SaaS product and Access CRM to handle authentication, govern access and orchestrate every API call per customer, at scale.
Your app requests an action for a specific customer.
Cyclr authenticates, applies policies and routes the request.
Access CRM processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore Access CRM methods you can orchestrate through Cyclr.
Retrieves the person specified by ID.
Retrieves all persons.
Retrieves all persons created or updated since the last successful run.
Retrieves all persons created since the last successful run.
List all attributes for applicants.
List all applicant's attributes.
List an applicant's attributes updated since the last successful cycle execution.
Retrieves all nationalities.
Retrieves the nationality specified by ID.
Retrieves the contents of all saved tag file lists.
Retrieves the contents of saved tag file lists related to the specified applicant.
Retrieves the contents of saved tag file lists related to the specified client.
Retrieves all saved tag file lists.
Retrieves the sector specified by ID.
Retrieves all sectors.
Retrieves contacts updated since the last time this action was executed. Requests can be separated into preset sizes, by number of pages returned
Retrieves clients updated since the last time this action was executed. Requests can be separated into preset sizes, by number of pages returned.
Retrieves applicants updated since the last time this action was executed. Requests can be separated into preset sizes, by number of pages returned
Retrieves the list value specified by ID. For example to retrieve the properties of a title object by Title Value ID.
Retrieves the user specified by ID.
Retrieves all contact attributes for the specified applicant.
Retrieves all contact attributes for the specified contact.
Retrieves all existing contact attributes, updated after the last cycle run.
Retrieves all contact attributes.
Retrieves the applicant specified by ID.
Retrieves applicants updated since the last time this action was executed.
Retrieves applicants created since the last time this action was executed.
Retrieves the applicant specified by primary email address.
Retrieves all applicants.
Retrieves applicants updated since the last time this action was executed. Requests can be separated into preset sizes, by number of days returned.
Retrieves all applicant stored docs.
Inserts the given Applicant's Mailshot "inOrOut" value
Gets a list of all new applicant mail options, created since the last cycle run.
Updates the given Applicant's Mailshot "inOrOut" and "optGlobal" value.
Retrieves all applicants.
Retrieves the custom fields for the specified applicant. The custom fields you wish to retrieve must be added to the response mappings with the key as the Field Location. (example: Field Location: bonus_paid or Field Location: cVProvided)
Retrieves all the applicants custom fields. The custom fields you wish to retrieve must be added to the response mappings with the key as the Field Location. (example: Field Location: [applicant].personID or Field Location: [applicant].applicantName).
Updates the given applicant Custom Fields value. The custom fields you wish to update must be added to the request mappings with the key as the Field Location. (example: Field Location: applicant.candidate_discipline_sought or Field Location: applicant.leadScore).
List all of the specified queriable objects fields.
Lists all queriable objects.
Retrieves jobs for the specified client.
Retrieves jobs for the specified contact.
Retrieves all jobs created since the last successful run.
Retrieves all jobs created or updated since the last successful run.
Retrieves all jobs.
Retrieves the job specified by ID.
Retrieves all placements.
Retrieves placements for the specified applicant.
Retrieves all placements created since the last successful run.
Retrieves all placements created or updated since the last successful run.
Retrieves placements for the specified contact.
Retrieves permanent placements for the specified client.
Bespoke endpoint, returns extra details for Permanent Placements.
Retrieves all permanent placements.
Retrieves permanent placements for the specified contact.
Retrieves permanent placements for the specified applicant.
Retrieves all placements created since the last successful run.
Retrieves all placements.
Retrieves all placements created or updated since the last successful run.
Retrieves the client specified by ID.
Retrieves clients created since the last time this action was executed.
Retrieves clients that have been created or updated since the last time this action was executed.
Retrieves all the clients custom fields. The custom fields you wish to retrieve must be added to the response mappings with the key as the Field Location. (example: Field Location: [clientCustomField].clientURN or Field Location: [clientCustomField].engagementType).
Updates the given applicant client Fields value. The custom fields you wish to update must be added to the request mappings with the key as the Field Location. (example: Field Location: client.clientURN or Field Location: client.sageRef).
Retrieves all clients.
Retrieves the custom fields for the specified client. The custom fields you wish to retrieve must be added to the response mappings with the key as the Field Location. (example: Field Location: clientCustomField.clientID or Field Location: clientCustomField.clientURN)
Retrieves clients updated since the last time this action was executed. Requests can be separated into preset sizes, by number of days returned.
Retrieves a contact consultant user by contact ID.
Retrieves all contact consultant users.
Run custom queries.
Retrieves timesheets updated since the last time this action was executed.
Retrieves timesheets for the specified client.
Retrieves all timesheets.
Retrieves timesheets created since the last time this action was executed.
Retrieves timesheets for the specified placement.
Retrieves the timesheet specified by ID.
Retrieves timesheets for the specified applicant.
Retrieves contacts created since the last time this action was executed. Custom Fields can be added to the response field mappings with a Field Location of [contact].customFields.<someField> eg. [contact].customFields.myCustomField
Retrieves the contact type specified by ID.
Retrieves all deleted contacts. Custom Fields can be added to the response field mappings with a Field Location of [contact].customFields.<someField> eg. [contact].customFields.myCustomField
Retrieves contacts updated since the last time this action was executed. Requests can be separated into preset sizes, by number of days returned.
Retrieves the contact specified by primary email address. Custom Fields can be added to the response field mappings with a Field Location of customFields.<someField> eg. customFields.myCustomField
Retrieves contacts updated since the last time this action was executed. Custom Fields can be added to the response field mappings with a Field Location of [contact].customFields.<someField> eg. [contact].customFields.myCustomField
Retrieves all contacts. Custom Fields can be added to the response field mappings with a Field Location of [contact].customFields.<someField> eg. [contact].customFields.myCustomField
Retrieves the contact specified by ID. Custom Fields can be added to the response field mappings with a Field Location of customFields.<someField> eg. customFields.myCustomField
Updates the given contact's Mailshot "inOrOut" value.
Inserts the given contact's Mailshot "inOrOut" value.
Gets a list of all new contact mail options, created since the last cycle run.
Retrieves all the Contacts custom fields. The custom fields you wish to retrieve must be added to the response mappings with the key as the Field Location. (example: Field Location: [contactCustomField].leadScoreContact or Field Location: [contactCustomField].sMSStatusContact)
Updates the given contact client Fields value. The custom fields you wish to update must be added to the request mappings with the key as the Field Location. (example: Field Location: contact.leadScoreContact or Field Location: contact.activityLinkContact).
Retrieves the custom fields for the specified contact. The custom fields you wish to retrieve must be added to the response mappings with the key as the Field Location. (example: Field Location: leadScoreContact or Field Location: sMSStatusContact)
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing Access CRM integrations in Cyclr.
Not specifiedIntegrator Key and API Key (issued by Access account manager).
Read, list, incremental sync, custom queries, update and insert actions for CRM objects.
Connector exposes incremental list endpoints and page-controlled incremental actions for updated or new records.
Refer to the vendor API documentation for current limits.
IMPLEMENTATION
Authentication uses two Access-supplied credentials — an Integrator Key and an API Key — configured in the Cyclr connector setup.
Integrator Key and API Key (issued by Access account manager).
Request Integrator Key and API Key from your Access account manager before setup.
COMMON QUESTIONS
It syncs Access CRM enquiries, persons/applicants, clients, jobs, placements and incremental updates so your app can read and update CRM records and run pipeline or marketing automations.
You authenticate with two Access-supplied credentials: an Integrator Key and an API Key, entered into the Cyclr connector setup.
Yes. Cyclr supports multi-tenant delivery and account-level isolation so you can deploy the same integration workflows across customer accounts while keeping credentials and data separated.
Yes. Cyclr lets you package connector methods and workflows into MCP servers and publish governed MCP-triggered workflows through an embedded marketplace or install per account.
KEEP EXPLORING
Related Crms connector for customer-facing integration workflows.
Related connectorRelated Crms connector for customer-facing integration workflows.
Related connectorRelated Crms connector for customer-facing integration workflows.