Microsoft Outlook currently provides 3 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New Email
Triggers when a new email is received in the inbox.
New Email in Folder
Triggers when a new email is delivered into the specified folder.
New Attachment
Triggers when a new email containing one or more attachments arrives.
Send Email
Sends an email using Microsoft Outlook.
Download Attachment
Download attachments from a specific email message.
Reply to Email
Reply to an outlook email.
Create Draft Email
Creates a draft email message.
Add Label to Email
Adds a category (label) to an email message.
Remove Label from Email
Removes a category (label) from an email message.
Request Approval in Email
Send approval request email and then wait until the email is approved or disapproved
Move Email to Folder
Moves an email message to a specific folder.
Send Draft Email
Sends a draft email message.
Forward Email
Forwards an email message.
Find Email
Searches for emails using full-text search.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Microsoft Outlook event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Email
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Microsoft Outlook action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Send Email
Combine Microsoft Outlook with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New Email
Finishes with
Send Email, then preserve the outcome in Coherence
The exact authentication fields depend on Microsoft Outlook. The workflow structure stays straightforward:
Authorize the Microsoft Outlook account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Microsoft Outlook or provide a complementary trigger or action.
Microsoft Outlook currently provides 3 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Microsoft Outlook currently lists 3 triggers and 12 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Microsoft Outlook triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
