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

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

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

Launch27
⚙
Microsoft Outlook
Authenticate Microsoft Outlook
Now, click the Microsoft Outlook node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Microsoft Outlook settings. Authentication allows you to use Microsoft Outlook through Latenode.
Configure the Launch27 and Microsoft Outlook 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 Launch27 and Microsoft Outlook 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
⚙
Microsoft Outlook
Trigger on Webhook
⚙
Launch27
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Launch27, Microsoft Outlook, 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 Launch27 and Microsoft Outlook integration works as expected. Depending on your setup, data should flow between Launch27 and Microsoft Outlook (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Launch27 and Microsoft Outlook
Launch27 + Microsoft Outlook + Google Calendar: When a new booking is created in Launch27, automatically send a confirmation email via Microsoft Outlook to the customer and create an event in Google Calendar.
Microsoft Outlook + Launch27 + Slack: When a new email arrives in Microsoft Outlook indicating a new Launch27 booking, the system extracts booking details (if possible) and sends a notification to a designated Slack channel.
Launch27 and Microsoft Outlook integration alternatives
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
About Microsoft Outlook
Automate email tasks with Microsoft Outlook in Latenode. Send personalized emails, track replies, or create calendar events based on triggers from other apps. Latenode lets you integrate Outlook with your CRM, database, or other tools in visual workflows. Manage email flow without manual work, customize it with code, and scale it on demand.
Similar apps
Related categories
See how Latenode works
FAQ Launch27 and Microsoft Outlook
How can I connect my Launch27 account to Microsoft Outlook using Latenode?
To connect your Launch27 account to Microsoft Outlook on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Launch27 and click on "Connect".
- Authenticate your Launch27 and Microsoft Outlook accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically email new Launch27 customers using Outlook?
Yes, you can! Latenode's visual editor makes it easy to trigger personalized emails in Microsoft Outlook upon new customer creation in Launch27, improving customer engagement and satisfaction.
What types of tasks can I perform by integrating Launch27 with Microsoft Outlook?
Integrating Launch27 with Microsoft Outlook allows you to perform various tasks, including:
- Automatically sending booking confirmations via Outlook.
- Creating Outlook calendar events for new Launch27 bookings.
- Sending reminder emails to customers before their appointments.
- Tracking customer feedback from emails in Launch27.
- Alerting your team via Outlook of urgent booking changes.
How can I customize data transferred from Launch27 to Outlook?
Latenode's JavaScript blocks let you transform Launch27 data before sending it to Microsoft Outlook, ensuring only relevant information is shared.
Are there any limitations to the Launch27 and Microsoft Outlook integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Large data transfers may be subject to API rate limits.
- Custom field mapping requires familiarity with data structures.
- Real-time synchronization depends on API availability and stability.