How to connect Contacts+ and Launch27
Create a New Scenario to Connect Contacts+ and Launch27
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 Contacts+, triggered by another scenario, or executed manually (for testing purposes). In most cases, Contacts+ or Launch27 will be your first step. To do this, click "Choose an app," find Contacts+ or Launch27, and select the appropriate trigger to start the scenario.

Add the Contacts+ Node
Select the Contacts+ node from the app selection panel on the right.


Contacts+

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


Contacts+
⚙
Launch27

Authenticate Launch27
Now, click the Launch27 node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Launch27 settings. Authentication allows you to use Launch27 through Latenode.
Configure the Contacts+ and Launch27 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 Contacts+ and Launch27 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
⚙
Launch27
Trigger on Webhook
⚙

Contacts+
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Contacts+, Launch27, 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 Contacts+ and Launch27 integration works as expected. Depending on your setup, data should flow between Contacts+ and Launch27 (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Contacts+ and Launch27
Contacts+ + Launch27 + Google Calendar: When a new contact is created in Contacts+, a booking is created in Launch27 for that customer. Then, a corresponding event is added to Google Calendar to schedule the cleaning service.
Launch27 + Contacts+ + Mailchimp: When a new booking is created in Launch27, the customer's contact information is added to Contacts+. This new contact is then automatically subscribed to a Mailchimp newsletter.
Contacts+ and Launch27 integration alternatives

About Contacts+
Use Contacts+ in Latenode to centralize contact data across platforms. Automate cleaning, deduplication, and enrichment processes. Sync updated contact details to your CRM or marketing tools. Latenode lets you build flexible flows and custom logic to manage contacts more efficiently and without manual data entry.
Similar apps
Related categories
About Launch27
Automate Launch27 booking & service management within Latenode. Create flows that sync bookings with calendars, trigger follow-ups based on booking status, or generate reports. Use Latenode's visual builder & JS node for custom logic, connecting Launch27 data to other apps without code limits. Scale operations with affordable, usage-based pricing.
Similar apps
Related categories
See how Latenode works
FAQ Contacts+ and Launch27
How can I connect my Contacts+ account to Launch27 using Latenode?
To connect your Contacts+ account to Launch27 on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Contacts+ and click on "Connect".
- Authenticate your Contacts+ and Launch27 accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically update Launch27 with new Contacts+ contacts?
Yes, you can! Latenode lets you sync new Contacts+ contacts to Launch27 automatically. Benefit from real-time data flow, ensuring your customer data is always up-to-date and accurate.
What types of tasks can I perform by integrating Contacts+ with Launch27?
Integrating Contacts+ with Launch27 allows you to perform various tasks, including:
- Automatically add new Contacts+ contacts to Launch27 as new customers.
- Update customer details in Launch27 when a contact is updated in Contacts+.
- Trigger Launch27 actions when a new contact is created in Contacts+.
- Create personalized welcome messages in Launch27 for new Contacts+ contacts.
- Segment contacts in Launch27 based on Contact+ contact list membership.
Can I use custom fields from Contacts+ within Launch27 workflows?
Yes! Latenode allows mapping custom fields from Contacts+ to Launch27, enabling workflows tailored to your unique data structure and business needs.
Are there any limitations to the Contacts+ and Launch27 integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require custom JavaScript code.
- Real-time synchronization depends on the API rate limits of both Contacts+ and Launch27.
- Historical data migration may require a separate, one-time workflow setup.