You are here:
Microsoft Outlook Connector
Connect to an external Microsoft Outlook account. Perform tasks like sending messages or creating events. Use Microsoft Outlook as a data source (trigger) or a data target (action).
Required Editions
| View supported editions. |
| This feature requires the MuleSoft for Flow: Integration add-on. Professional Edition requires the API access add-on. To purchase, contact your Salesforce account executive. |
| MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive. |
Microsoft 365 Subscription Plan Requirements
- Microsoft Outlook Connector performs optimally in MuleSoft for Flow: Integration with an active Microsoft 365 subscription. For details on subscription plans, see the Microsoft 365 plan options documentation.
- To use Microsoft Outlook Connector with a trial Microsoft 365 subscription, contact Microsoft Support through the Admin Portal to ensure your trial account has the necessary permissions for sending and receiving emails.
Connections
To connect to a system, whether it's a data source or a data target, create a connection with that system's standard connection or with an existing external named credential. You can connect to multiple systems within a flow and reuse each connection. You can create connections in the Integrations tab or in Flow Builder.
Standard Connection
This system uses OAuth2ClientCredentials authentication.
OAuth2ClientCredentials authentication obtains an access token from a user-defined path.
This system requires this credential information for its connections.
| FIELD | DESCRIPTION |
|---|---|
| Connection Name | Enter a unique connection name that helps you remember the details of this connection. Salesforce hides the credentials after you create the connection. Reuse connections as needed. Anyone with the Manage Integration Connections permission can see and use all connections in the org. |
| ClientId | Enter the OAuth client ID to use to authenticate the requests. |
| ClientSecret | Enter the OAuth client secret to use to authenticate the requests. |
| URL | Enter the URL to use to authenticate the requests. |
| Scope | Enter the scopes that the client can access. |
| Token URL | Enter the URL to use to get an access token. |
Named Credential Connection
Select a pre-existing named credential from Setup to use for your external system connections.
Before connecting to your external system with a named credential, first create or use an existing authenticated named credential and external credential that is enabled for your users.
To ensure a successful connection for use in a flow, use only one principal for each named credential.
- Use the same name for the named credential and its related objects, such as the external credential and external authentication identity providers. Labels for these objects can differ.
- Assign the user creating the connection the required user permission for the principal. Without this permission, the connection test fails and the connection remains inactive.
When you create a connection with an existing named credential, note these behaviors:
- Manage the named credential’s read-only details in Setup, not the Integrations tab. On the Integrations tab, you can only edit the connection's Connection Name and Description.
- Perform reconnections for the named credential in Setup. The Reconnect button isn’t visible on the Details page.
- Delete associated named credentials in Setup. Deleting a connection doesn't remove the credential.
Triggers
A trigger initiates the flow when a specified event occurs. Triggers are important for automating business processes because they react to real-time data changes in various systems. For more information about triggers, refer to Create a Flow with a Connector as a Trigger.
These Microsoft Outlook triggers are available in Flow Builder.
- On New Contact
- On New Event
- On New Message
- On New Or Update Contact
- On New Or Update Event
- On New Or Update Message
Actions
An action performs a specific task or operation within a target system. Use actions to automate tasks across different systems without manual intervention, based on conditions set in the flow. For more information about actions, refer to Create a Flow with a Connector as an Action.
These Microsoft Outlook actions are available in Flow Builder.
- Assign License
- Create Calendar
- Create Calendar Event
- Create Event
- Create Message
- Create User
- Delete Event
- End Out Of Office Early
- Get Calendar
- Get Event
- Get Message
- Get Schedule
- List Calendar
- List Event
- Lookup Calendar Availability
- Patch Calendar
- Search Mails
- Send Message
- Set Out Of Office Status
- Update Calendar
- Update Event
- Update Message
- Microsoft Entra ID, in which you go to Users, select the user, and then locate the object ID.
- Microsft Entra ID Connector, in which you use the Get User By Id action and provide the user's email address.
For information about specific limitations for connections and third-party connectors, see MuleSoft for Flow: Integration Limits & Considerations.
