Faster time to value
Ship integrations weeks faster than building from scratch
SalesNexus Connector
Build embedded, customer-facing integrations that create and sync SalesNexus contacts, add contacts to campaigns, schedule activities and fetch contact details — all inside your SaaS product using Cyclr’s orchestration and white‑label marketplace.
Reusable orchestration
Create templates once, reuse across customers and workflows
Governed MCP tools
Expose approved methods as managed, versioned tools
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
What you can integrate or automate with SalesNexus
Integrate SalesNexus contact, campaign and activity workflows — create and update contacts, add contacts to campaigns, schedule activities, fetch field metadata and run searches. Cyclr orchestrates these SalesNexus API calls into reusable, multi-step templates you can embed in your product, govern as MCP tools and publish to customers. See the SalesNexus API documentation for function details. (logon.salesnexus.com)
PRODUCT USE CASES
Why teams choose embedded SalesNexus integrations
Cyclr helps product and engineering teams publish in-app SalesNexus automations: sync leads to SalesNexus contacts, trigger email campaigns, create tasks and surface contact data in your UI — all managed and governed from your Console.
Sync app leads to SalesNexus contacts
Automatically create-contact and update-contact in SalesNexus when a lead is captured in your app (uses create-contact, update-contact). (logon.salesnexus.com)
Add users to SalesNexus campaigns
Add contacts to campaigns and trigger campaign workflows using add-to-campaign and get-contacts. (logon.salesnexus.com)
Create sales activities and tasks
Schedule and assign activities in SalesNexus after product events using create-activity and get-activities. (logon.salesnexus.com)},{
ORCHESTRATION
How SalesNexus works with Cyclr
Cyclr sits between your SaaS product and SalesNexus to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
SalesNexus
SalesNexus processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore SalesNexus methods you can orchestrate through Cyclr.
Authentication1
Get API Key
ActionObtains a temporary API Key to be used for subsequent requests.
Sales2
List Sales
ActionLists all sales.
List New Sales
ActionLists sales created since the last run.
Contacts4
List Contacts
ActionLists all contacts associated with the authenticated user.
List New Contacts
ActionLists contacts created since the last run.
List Updated Contacts
ActionLists contacts updated since the last run.
Get Contact
ActionGets all information associated with a contact.
TECHNICAL DETAILS
SalesNexus integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing SalesNexus integrations in Cyclr.
API and authentication
- API host
https://logon.salesnexus.com/api/call-v1- Authentication
- API key; Authorization token
- Credentials
Enter the SalesNexus API Key; temporary token obtainable via Get API Key using email and password in the connector test tab.
- Method categories
Contacts, Activities, Campaigns, Sales Opportunities, Groups, Users, Session and Field management
Pagination and rate limits
Pagination
Cursor-like paging using start-after and page-size parameters; ordered results are guaranteed for sequential paging. (logon.salesnexus.com)
Rate limits
No public rate-limit details in API documentation; implement retries/backoff and confirm limits with SalesNexus support. (logon.salesnexus.com)
IMPLEMENTATION
Authentication at a glance
SalesNexus uses an API key plus a per-client authorization/session token. Temporary tokens can be obtained via get-login-token; request permanent keys from SalesNexus support. Confirm enabled options in Cyclr Console. (logon.salesnexus.com)
- Authentication method
- API key; Authorization token
- Credential required
Enter the SalesNexus API Key; temporary token obtainable via Get API Key using email and password in the connector test tab.
Before you begin:
View setup guideTemporary tokens expire; request a permanent API key from SalesNexus for stable production use. (community.cyclr.com)
COMMON QUESTIONS
Frequently asked questions
It can create and update contacts, add contacts to campaigns, schedule or complete activities, fetch field metadata and run contact searches. These map to documented SalesNexus functions like create-contact, add-to-campaign and get-contacts. (logon.salesnexus.com)
Use a SalesNexus API Key plus an authorization (session) token. Temporary tokens are obtained with get-login-token (email/password); permanent keys are available via SalesNexus support. (logon.salesnexus.com)
Yes. Cyclr supports multi-tenant embedding: store per-tenant SalesNexus keys and tokens, run cycles per account and surface integrations inside your product UI. Governance and tenant credential management are handled in the Cyclr Console. (community.cyclr.com)
Yes. You can expose approved SalesNexus methods as versioned MCP tools in Cyclr, enabling product teams to control which steps partners or customers may use. Confirm available methods in the connector methods list. (community.cyclr.com)
KEEP EXPLORING
Related resources and connectors
Documentation
Email Marketing Integrations to make your daily tasks easier
Read more →ProductCRM Integrations you should be using
Read more →ProductMCP PaaS
Read more →Related connectorActiveCampaign
Related Crms connector for customer-facing integration workflows.
Related connectorGist
Related Crms connector for customer-facing integration workflows.
Related connectorLead Squared
Related Crms connector for customer-facing integration workflows.