Faster time to market
Ship guest-sync and marketing automations quickly without custom integration work
Sprout Send Connector
Build in‑app Sprout Send integrations to sync guest and contact records, export campaign recipients, create offers and ingest visits or transactions. Use Cyclr to embed these automations inside your SaaS and deliver customer-facing marketing workflows without building the connector yourself.
Governed MCP tools
Expose approved Sprout Send actions as controlled tools for your customers
Multi-tenant OAuth handling
Manage per-tenant OAuth apps and tokens centrally for each customer
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Integrate guest and contact records, campaign exports, forms, offers, visits and transactions and automate campaign recipient exports, contact updates and voucher creation. Cyclr uses Sprout Send’s OAuth 2.0 API so you register an app and provide a Cyclr callback URL to enable connector installs. See the Sprout Send API documentation for endpoints and request patterns. (apidocs.sproutsend.com)
PRODUCT USE CASES
Use cases
Quickly create guest-sync, campaign export and voucher workflows, then publish them into your product through Cyclr’s embedded marketplace for end customers to install and run.
Sync contacts and guest profiles
Create and update Sprout Send contacts (POST /contacts, PUT /contacts/:_id) to keep guest profiles synced between systems. (apidocs.sproutsend.com)
Export campaign recipients and reporting
Export campaign folders, channel lists and recipients (GET /campaigns/export and recipients export) to feed reporting or trigger downstream workflows. (apidocs.sproutsend.com)
Create offers and vouchers
Create hospitality offers and vouchers using the Offers API (POST /offers) to automate promotions from your product. (apidocs.sproutsend.com)
ORCHESTRATION
How Sprout Send works with Cyclr
Cyclr sits between your SaaS product and Sprout Send 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
Sprout Send
Sprout Send 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 Sprout Send methods you can orchestrate through Cyclr.
Contacts5
Delete Contract
ActionDelete an existing contact using ID.
Create Contact
ActionCreate a new contact.
List Contacts
ActionList all Contacts
Create Contacts
ActionBatch create contacts, capable of doing 100 contacts per request.
Update Contact
ActionUpdate an existing contact.
metadata1
Create Field
ActionCreate a custom field for a contact.
TECHNICAL DETAILS
Sprout Send integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Sprout Send integrations in Cyclr.
API and authentication
- API host
https://apidocs.sproutsend.com/- Authentication
- OAuth 2.0
- Credentials
Client ID; Client Secret; Callback URL (use your Cyclr service domain); admin privileges required.
- Method categories
Accounts; Contacts; Campaigns; Campaign channels; Forms; Fields; Offers; Transactions; Visits. (apidocs.sproutsend.com)
Pagination and rate limits
Pagination
Supports page and pageSize query parameters; collection responses include pagination links and totalPage meta. (apidocs.sproutsend.com)
Rate limits
3,600 requests/hour per account; 150 requests/minute per IP; 30 requests per 10 seconds per IP. Excess calls return 429. (apidocs.sproutsend.com)
IMPLEMENTATION
Authentication at a glance
Sprout Send uses OAuth 2.0 with client_id and client_secret; register an OAuth app and use Cyclr’s callback URL when creating the app. Cyclr stores client credentials for connector installs. (apidocs.sproutsend.com)
- Authentication method
- OAuth 2.0
- Credential required
Client ID; Client Secret; Callback URL (use your Cyclr service domain); admin privileges required.
Before you begin:
View setup guideRegister an OAuth app in Sprout Send, add the Cyclr callback URL and use an admin account. (community.cyclr.com)
COMMON QUESTIONS
Frequently asked questions
It syncs guest and contact records, exports campaign folders and recipients, manages forms and submissions and creates offers, visits and transactions. The connector maps to Sprout Send endpoints such as contacts, campaigns, forms, offers, visits and transactions. (apidocs.sproutsend.com)
It uses OAuth 2.0. Register an OAuth app in Sprout Send to obtain a client_id and client_secret, set the Cyclr callback URL when creating the app, and add those credentials in the Cyclr Console. (apidocs.sproutsend.com)
Yes. Cyclr supports multi-tenant installs by centrally storing OAuth credentials and installing the connector per customer account, letting you run isolated automations for each tenant. (community.cyclr.com)
Yes. You can package Sprout Send actions as reusable, governed MCP tools in Cyclr, so product and security teams control which methods customers can run. (community.cyclr.com)
KEEP EXPLORING
Related resources and connectors
Documentation
CRM Integrations you should be using
Read more →ProductWhat is iPaaS?
Read more →ProductMCP PaaS
Read more →Related connectorActiveCampaign
Related Crms connector for customer-facing integration workflows.
Related connectorBitrix24
Related Crms connector for customer-facing integration workflows.
Related connectorCapsule
Related Crms connector for customer-facing integration workflows.