How to connect Campaign Monitor and Kintone
Create a New Scenario to Connect Campaign Monitor and Kintone
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Campaign Monitor, triggered by another scenario, or executed manually (for testing purposes). In most cases, Campaign Monitor or Kintone will be your first step. To do this, click "Choose an app," find Campaign Monitor or Kintone, and select the appropriate trigger to start the scenario.

Add the Campaign Monitor Node
Select the Campaign Monitor node from the app selection panel on the right.

Campaign Monitor
Configure the Campaign Monitor
Click on the Campaign Monitor node to configure it. You can modify the Campaign Monitor URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Kintone Node
Next, click the plus (+) icon on the Campaign Monitor node, select Kintone from the list of available apps, and choose the action you need from the list of nodes within Kintone.

Campaign Monitor
⚙
Kintone
Authenticate Kintone
Now, click the Kintone node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Kintone settings. Authentication allows you to use Kintone through Latenode.
Configure the Campaign Monitor and Kintone Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Campaign Monitor and Kintone Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Kintone
Trigger on Webhook
⚙
Campaign Monitor
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Campaign Monitor, Kintone, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Campaign Monitor and Kintone integration works as expected. Depending on your setup, data should flow between Campaign Monitor and Kintone (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Campaign Monitor and Kintone
Campaign Monitor + Kintone + Slack: When a new subscriber is added to Campaign Monitor, a new record is created in Kintone, and a notification is sent to a Slack channel.
Campaign Monitor + Kintone + Google Sheets: When a new email is opened in Campaign Monitor, the corresponding record in Kintone is updated, and the campaign data is then added to Google Sheets.
Campaign Monitor and Kintone integration alternatives
About Campaign Monitor
Use Campaign Monitor in Latenode to automate email marketing based on triggers from other apps. Sync contact lists, personalize campaigns, and track results directly within your workflows. Latenode adds scheduling, conditional logic, and data transformation for sophisticated, automated outreach, bypassing Campaign Monitor's limits.
Similar apps
Related categories
About Kintone
Integrate Kintone into Latenode to automate custom application workflows. Sync data, trigger actions, and manage processes without code. Extend Kintone's capabilities with Latenode's visual builder, JavaScript functions, and AI tools to automate data validation, reporting, and notifications. Scale efficiently and only pay for what you use.
Related categories
See how Latenode works
FAQ Campaign Monitor and Kintone
How can I connect my Campaign Monitor account to Kintone using Latenode?
To connect your Campaign Monitor account to Kintone on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Campaign Monitor and click on "Connect".
- Authenticate your Campaign Monitor and Kintone accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I sync new Campaign Monitor subscribers to Kintone?
Yes, you can! Latenode lets you automatically sync new subscribers to Kintone, creating new records with no code. Keep contact data consistent and up-to-date across platforms.
What types of tasks can I perform by integrating Campaign Monitor with Kintone?
Integrating Campaign Monitor with Kintone allows you to perform various tasks, including:
- Add new Campaign Monitor subscribers as new Kintone records.
- Update Kintone records when subscriber details change in Campaign Monitor.
- Trigger Campaign Monitor campaigns based on Kintone record updates.
- Create personalized email campaigns from data within Kintone apps.
- Track campaign performance data in Kintone for detailed reporting.
Can I use JavaScript to customize Campaign Monitor data in Latenode?
Yes! Latenode's JavaScript blocks allow complex data transformations and enrichments before updating Kintone, providing unmatched integration flexibility.
Are there any limitations to the Campaign Monitor and Kintone integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require JavaScript knowledge.
- Initial data migration from Campaign Monitor to Kintone must be handled separately.
- Large data volumes may impact workflow execution time.