Faster delivery
Ship Act! automations faster with prebuilt actions and low-code mapping.

Build in-app integrations that sync Act! contacts, opportunities and activities, trigger email campaigns and automate lead routing for your customers — all managed and deployed from Cyclr.
Ship Act! automations faster with prebuilt actions and low-code mapping.
Create once and reuse workflows across customer accounts and environments.
Manage credentials, access and versions per customer tenant securely.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Teams can integrate Act! contacts, companies, opportunities, activities and email marketing to sync customer data, automate lead routing and trigger campaign sends. Using Act! Web API’s REST surface and OData reads, Cyclr orchestrations map fields, create or update records, register webhook monitors and run batched requests per tenant.
PRODUCT USE CASES
Quickly build and deploy tenant-scoped automations: synchronize signups to Act! contacts, create opportunities from in-app events, log activities and trigger email campaigns — all from your product UI using Cyclr orchestration and governance.
When a customer signs up in your app, create or update a Contact and add to an Act! Group for segmented campaigns.
Convert qualified product events into Act! Opportunities and assign owners, stages and expected close dates.
Write Activities to Act! when users complete tasks, attend demos or respond to support — keeping sales context current.
ORCHESTRATION
Cyclr sits between your SaaS product and Act! 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.
Act! processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore Act! methods you can orchestrate through Cyclr.
Get all users.
Gets basic system information, no auth needed.
Get a specific contact.
Get all contacts.
Get all contacts with a given email address.
Create a new Contact.
Update an already existing contact.
Get all contact(s) that are associated with a given opportunity.
Delete an existing contact.
Get new contacts since last run time.
Get updated contacts since last run time.
Delete an existing opportunity.
Get all opportunities.
Update an already existing opportunity product.
Create a new opportunity product.
Get new opportunities since the last run time.
Get updated opportunities since the last run time.
Create a new Opportunity.
Update an already existing opportunity.
Get a specific opportunity product.
Get a specific opportunity.
Associate the contact (if it is not already present) to a opportunity.
Get all contact opportunities.
Get all processes.
Get an opportunity process.
Get all products associated with an opportunity.
Create a new Marketing Automation Email.
Get all history items.
Get all history items for a contact created since last run.
Get all history items for a contact.
Get all history items for a contact created or modified since last run.
Get the last history item created or updated for a contact.
Get all groups.
Get all custom entity data matching an (optional) OData query.
Get a specific custom entity.
Delete an existing custom entity.
Create a new custom entity.
Create a new custom entity.
List fields for an object (company, contact, etc) created or updated since last run time.
List fields for an object (company, contact, etc).
List fields for an object (company, contact, etc) created since last run time.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing Act! integrations in Cyclr.
https://{server}/act.web.apiUsername, password (Basic) to obtain token; Act-Database-Name header; optional webhook callback token.
Contacts, Companies, Opportunities, Activities, Groups, Email/Marketing, Webhooks, OData reads and CRUD
Collection reads accept OData v4 ($top, $skip) plus $filter, $orderby, $select, $expand. Batch requests via POST /api/$batch.
Refer to the vendor API documentation for current limits.
IMPLEMENTATION
Act! Web API uses HTTP Basic to obtain a JWT bearer token. Requests use Authorization: Bearer and require an Act-Database-Name header. API is JSON REST-based.
Username, password (Basic) to obtain token; Act-Database-Name header; optional webhook callback token.
Webhooks require self-hosted Act! Premium Web and webhook service installation.
COMMON QUESTIONS
It syncs and manages Act! Contacts, Companies, Opportunities, Activities and email/marketing sends. Cyclr workflows can create, update, read and batch those records, and register webhook monitors for changes.
Act! uses Basic auth to obtain a JWT bearer token. You call /authorize with Basic credentials and include Act-Database-Name; then use Authorization: Bearer on requests.
Yes. Cyclr workflows use per-customer Act! credentials and tenant-scoped endpoints so you can embed the same orchestration across multiple customer accounts with separate credentials.
Yes. You can expose Act! CRUD and marketing actions as Cyclr MCP tools with governance, versioning and controlled access so product teams manage which methods customers can run.
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.