Post Meeting Actions MCP server

The Post Meeting Actions MCP server enables LLMs to interact with Salesforce, Gong, Zoom, Gmail, and Outlook for processing a completed sales call end-to-end through natural conversation. It provides tools to retrieve the Salesforce record and call transcript, generate a summary in your configured sales methodology, and write it to Salesforce, with resource lookup and a follow-up email available on request. Each deployment implements only the tools for its configured transcript source(s) and email platform(s).

Uses

Use the Post Meeting Actions MCP server to perform the following actions:

  • Process a completed sales call end-to-end: Find the Salesforce record, retrieve the call transcript, generate a summary, and write it to Salesforce
  • Find the Salesforce Opportunity related to a call or meeting
  • Retrieve a call transcript from Gong or Zoom
  • Search within a call's transcript for a specific mention or topic without regenerating the whole summary
  • Generate a call summary structured to your org's configured sales methodology
  • Check which sales methodology and Salesforce fields this deployment is configured to write to
  • Write a summary to Salesforce as Opportunity fields and a Task
  • Retrieve relevant customer stories or product resources to support a follow-up
  • Draft and send a follow-up email to a prospect through Gmail or Outlook
  • Check which of your calls have outstanding summarization, writing, or follow-up steps

Example prompts

Use the following example prompts to invoke Post Meeting Actions MCP server tools:

  • Process my call with Acme.
  • Update Salesforce based on my latest call with Acme.
  • Find my last call with Acme.
  • Search my call with Acme for any mention of budget.
  • Format my call notes using our sales methodology.
  • What competitors were mentioned in my call with Acme?
  • Draft a follow-up email for my call with Acme, including relevant case studies.
  • Send the follow-up email once I approve it.
  • Pull my calls with pending follow-up actions.
  • What have I not finished processing yet?

Post Meeting Actions MCP server tools

The Post Meeting Actions MCP server provides the following tools:

ToolDescription
find_target_recordFinds the Salesforce Opportunity related to a meeting.
search_call_activitiesFinds Salesforce activity history for logged calls or meetings for a specific account and a date range.
retrieve_call_transcript_gongRetrieves transcript and metadata for a Gong-sourced call.
retrieve_call_transcript_zoomRetrieves transcript and metadata for a Zoom-sourced call.
generate_meeting_summaryProduces a summary mapped to the configured sales methodology.
get_salesforce_write_policyReturns the configured sales methodology and the Salesforce fields allowed for post-meeting writes.
write_summary_to_system_of_recordWrites the confirmed summary to Salesforce as Opportunity fields and a Task, with an optional linked Note.
retrieve_kb_resourcesRetrieves supporting customer stories or product resources.
search_transcript_chunksRetrieves chunked transcript documents for a call, or runs a semantic search across transcript chunks.
draft_followup_email_gmailDrafts a follow-up email to a prospect through Gmail, optionally with supporting resources.
draft_followup_email_outlookDrafts a follow-up email to a prospect through Outlook, optionally with supporting resources.
send_followup_email_gmailSends an approved follow-up email through Gmail.
send_followup_email_outlookSends an approved follow-up email through Outlook.
list_pending_meetingsLists meetings this server has started processing but hasn't finished.

Install the Post Meeting Actions MCP server

Complete the following steps to install a prebuilt MCP server to your project:

1

Sign in to your Workato account.

2

Go to AI Hub > Enterprise MCP.

3

Click + Create MCP server.

4

Go to the Start with pre-built MCP Servers using your connected apps section and select the prebuilt MCP server you plan to use.

5

Click Use this server.

6

Provide a name for your MCP server in the Server name field.

7

Use the Location drop-down menu to select the project for the MCP server.

8

Go to the Connections section and connect to your app account.

9

Select the connection type you plan to use for the MCP server template.

  • User's connection: MCP server tools perform actions based on the identity and permissions of the user who connects to the application. Users authenticate with their own credentials to execute the skill.
  • Your connection: This option uses the connection established by the recipe builder and follows the same principles as normal app connections.

Select your connection typeSelect your connection type

VERIFIED USER ACCESS AUTHENTICATION REQUIREMENTS

Only app connections that use OAuth 2.0 authorization code grant are available for user's connection. Refer to Verified user access for more information.

10

Complete the app-specific connection setup steps in the following section.

Post Meeting Actions connection setup

Configure the following connections to set up the Post Meeting Actions MCP server:

  • Salesforce: Required.
  • Gong: Optional. Connect to Gong to retrieve Gong-sourced call transcripts.
  • Zoom: Optional. Connect to Zoom to retrieve Zoom-sourced call transcripts.
  • Gmail: Optional. Connect to Gmail to draft and send follow-up emails through Gmail.
  • Outlook: Optional. Connect to Outlook to draft and send follow-up emails through Outlook.

Post Meeting Actions role requirements

Each tool's availability depends on the permissions granted to its connected account:

  • Salesforce: Requires write access to the Task object, and create access to ContentNote and ContentDocumentLink when the system_of_record.write_content_note project property is enabled. A missing permission returns a permission_denied outcome rather than a partial result.
  • Gong: Requires access to basic call metadata and the transcript body. A connection missing the transcript scope still returns call metadata and Gong's own summary.
  • Zoom: Requires access to transcripts and AI-generated meeting summaries. A connection missing the summary scope still returns the transcript.
  • Gmail and Outlook: Requires access to draft and send email on behalf of the connected mailbox.

Salesforce connection setup steps

View Salesforce connection setup steps

Workato supports OAuth 2.0 authentication and JWT bearer authentication connections for Salesforce.

Salesforce OAuth 2.0 authentication
View OAuth 2.0 authentication steps

Connect to Salesforce using OAuth 2.0 (Authorization Code Grant)

Complete the following steps to set up an OAuth 2.0 (Authorization Code Grant) connection to Salesforce in Workato:

OAUTH RESTRICTIONS

As of early September 2025, Salesforce restricts the use of uninstalled Salesforce Connected Apps. Refer to OAuth restrictions for required actions if you encounter errors when you create a new connection. These steps are required for all new Salesforce connections starting September 17, 2025.

1

Click Create > Connection or press C twice.

2

Search for Salesforce and select it as your app.

3

Enter a name in the Connection name field.

Salesforce connection setupOAuth2.0 Salesforce connection setup

4

Use the Location drop-down menu to select the project where you plan to store the connection.

5

Use the Auth type drop-down menu to select OAuth 2.0 (Authorization Code Grant).

6

Use the Sandbox drop-down menu to specify whether the Salesforce account is a sandbox account.

7

Optional. Expand Advanced settings to configure the following options:

Advanced settings
  • Organization/community custom domain URL: Enter the URL to your Salesforce community's custom domain. Required for community connections with unique domains.
  • Requested permissions: Select permissions to request for this connection. Refer to Minimum and default scopes for the scopes Workato requests by default.
  • Verified user access configuration: Configure custom auth for personal connections. Refer to Runtime user connections for more information.

REFRESH TOKEN SCOPE IS REQUIRED

The Perform requests at any time scope is one of Workato's minimum scopes for OAuth 2.0 connections, but whether Salesforce actually grants this scope depends on the Connected App's own OAuth policies, not on the Workato connection's settings. Refer to Salesforce connection disconnects repeatedly if your connection later disconnects when the access token expires. A Refresh Token Policy or IP Relaxation setting can cause the same symptom.

8

Optional. Use the Custom OAuth profile drop-down menu to select a custom OAuth profile for your connection. Refer to Create a custom OAuth profile for Salesforce for more information.

9

Click Connect.

10

Optional. If your Salesforce organization or community uses a custom domain, complete the following in the sign-in modal:

  • Click Use Custom Domain.
  • Enter your Custom domain, then click Continue.

Salesforce custom domainsEnter your Custom domain.

11

Enter your Salesforce Username and Password.

Salesforce connection setupLog in to your Salesforce account

12

Click Log In to complete the setup.

OAUTH_APPROVAL_ERROR_GENERIC

If you see this error, Salesforce is restricting the Workato app because it isn't installed. A Salesforce admin must install the app in Connected Apps OAuth Usage or assign the Salesforce permissions. Refer to OAuth restrictions for details.

Salesforce JWT bearer authentication
View JWT bearer authentication steps

ACTIONS ON BEHALF OF USER

JWT connections can perform actions on behalf of a user you specify using the On-behalf-of-user email field. Contact your Workato Customer Success Manager to enable this feature.

How it works

JWT bearer authentication connects using a digital certificate that signs a JWT request. Workato sends a JWT to the Salesforce OAuth token endpoint, where Salesforce processes the JWT and issues an access token based on prior approval of Workato in Salesforce.

Although JWT bearer skips interactive sign-in, Salesforce still evaluates every request against the permissions of the user specified in the connection and attributes any changes to that user. Use a dedicated integration user rather than a personal account.

Refer to Required roles and permissions for the Salesforce permissions the connected user needs.

Generate a private key and certificate

JWT bearer authentication requires a private key and a certificate. The following command generates both using OpenSSL. Replace the -subj values with your own:

bash
openssl req -x509 -sha256 -nodes -newkey rsa:2048 \
  -keyout server.key \
  -out server.crt \
  -days 365 \
  -subj "/CN=Your App Name/O=Your Organization/C=US"

This generates two files:

FileDescription
server.keyYour private key for Workato. Keep this secret.
server.crtYour public certificate for Salesforce.

Refer to Salesforce's documentation for more information:

Create an external client app for JWT bearer

JWT bearer authentication also requires a registered external client app in Salesforce. Complete the following steps before creating your connection in Workato. Refer to Salesforce's Create an External Client App documentation for more information.

1

Sign in to Salesforce.

2

Go to Setup > Apps > External Client Apps > External Client App Manager.

3

Click New External Client App.

4

Enter a name in the External Client App Name field, such as Workato.

5

Enter a name in the API Name field that meets the following requirements:

  • Contains only underscores and alphanumeric characters.
  • Is unique.
  • Starts with a letter.
  • Doesn't include spaces.
  • Doesn't end with an underscore.
  • Doesn't contain consecutive underscores.
6

Enter the contact email address for your app in the Contact Email field.

7

Use the Distribution State drop-down menu to select either Local or Packaged.

8

Expand API (Enable OAuth Settings) and select the Enable OAuth checkbox. Refer to Salesforce's Configure the External Client App OAuth Settings documentation for more information.

9

Enter https://www.workato.com/oauth/callback in the Callback URL field.

10

Select your OAuth scopes in the OAuth Scopes field based on the actions and triggers you plan to use, then click the Move selection to Selected OAuth Scopes arrow to apply them.

Configure scopes for your external client appConfigure scopes for your external client app

REFRESH_TOKEN SCOPE IS REQUIRED

If you see the error refresh_token scope is required and the connected app should be installed and preauthorized, add Perform requests at any time (refresh_token, offline_access) to your OAuth scopes. If you then see an invalid session error, also add Manage user data via APIs (api).

11

Select Enable JWT Bearer Flow in the Flow Enablement section. Refer to Salesforce's Configure a JWT Bearer Flow documentation for more information.

12

Upload server.crt as the digital certificate.

13

Click Create.

14

Click the Policies tab, then click Edit.

15

Expand the OAuth Policies section and set Permitted Users to Admin approved users are pre-authorized.

USER HASN'T APPROVED THIS CONSUMER

If you see this error when connecting, this step was likely missed.

16

Locate the App Policies section. Add either the profile or permission set assigned to the Salesforce user Workato connects as to the Select Profiles or Select Permission Sets list. Refer to Salesforce's Preauthorize User App Access Through External Client App Policies documentation for more information.

USER IS NOT ADMIN APPROVED TO ACCESS THIS APP

If you see this error when connecting, this step was likely missed.

17

Click Save.

18

Click the Settings tab for your external client app.

19

Expand the OAuth Settings section.

20

Click Consumer Key and Secret.

21

Verify your identity when prompted.

22

Copy the Consumer Key. You'll enter this as the Issuer when connecting in Workato.

Connect to Salesforce using JWT bearer

Complete the following steps to connect to Salesforce using JWT bearer authentication:

1

Click Create > Connection or press C twice.

2

Search for Salesforce and select it as your app.

3

Enter a name in the Connection name field.

Salesforce JWT ConnectionConfigure Salesforce JWT Bearer connection

4

Use the Location drop-down menu to select the project where you plan to store the connection.

5

Use the Auth type drop-down menu to select JWT token.

6

Use the Sandbox drop-down menu to specify whether the Salesforce account is a sandbox account.

7

Paste the full contents of server.key in the Private key field, including the -----BEGIN PRIVATE KEY----- and -----END PRIVATE KEY----- lines.

8

Enter the Consumer Key from your external client app in the Issuer field.

9

Enter the Subject for the JWT connection. This is the username of the Salesforce user you want Workato to authenticate as, or a valid Experience Cloud username if you're connecting to an Experience Cloud site. You can use principal (prn) in place of subject (sub) for backward compatibility. If you specify both, Workato uses prn.

10

Enter your Salesforce Subdomain. For example, if your Salesforce URL is yourInstance.salesforce.com, the subdomain is yourInstance.

11

Optional. Use the Custom OAuth profile drop-down menu to select a custom OAuth profile for your connection. Refer to Create a custom OAuth profile for Salesforce for more information.

12

Click Connect.

Gong connection setup steps (optional)

View Gong connection setup steps

REQUIRED PROJECT PROPERTY

Include gong in the transcript_source.enabled_sources project property to retrieve Gong-sourced call transcripts.

The Gong connector uses OAuth 2.0 authentication.

Gong minimum and default scopes

Workato requires the api:users:read scope. Refer to the Gong API documentation for more detailed information about the available scopes.

Gong setup

Complete the following steps in Gong to generate credentials:

1

Sign in to your Gong developer instance. Refer to Request a developer instance for more information.

2

Go to Admin center.

Admin centerAdmin center

3

Click API in the Ecosystem section.

4

Click CREATE INTEGRATIONS in the INTEGRATIONS tab.

5

Complete the CREATE YOUR GONG INTEGRATION page, including name, description, and required authorization scopes. Refer to Submit your integration details to Gong for more information.

SELF-SERVICE (WORKATO FREE, WORKATO PRO, OR DEVELOPER SANDBOX) WORKSPACES

If you created your workspace as a Self-service user, use https://app.trial.workato.com/oauth/callback as the redirect URI or callback URL when you configure the OAuth integration.

6

Click Save. Your integration information appears as a new row in the list of integrations.

7

Copy and save the CLIENT ID and CLIENT SECRET for use in Workato.

Connect to Gong with OAuth 2.0

Complete the following steps to connect to Gong in Workato:

1

Click Create > Connection or press C twice.

2

Search for Gong.io and select it as your app.

3

Enter a name for your connection in the Connection name field.

Connect to GongConnect to Gong

4

Use the Location drop-down menu to select the project where you plan to store the connection.

5

Expand the Advanced settings section to configure Scopes for your connection. Workato requests all available scopes by default. You can select granular scopes from the multi-select list to limit access.

6

Enter the Client ID and Client secret. Refer to Gong setup for more information.

7

Optional. Use the Custom OAuth profile drop-down menu to select a custom OAuth profile for your connection.

8

Click Connect.

9

Sign in to Gong using your credentials when prompted.

10

Click Allow to provision access to Workato.

Zoom connection setup steps (optional)

View Zoom connection setup steps

REQUIRED PROJECT PROPERTY

Include zoom in the transcript_source.enabled_sources project property to retrieve Zoom-sourced call transcripts.

The Zoom connector uses OAuth 2.0 authentication.

Complete the following steps to connect to Zoom in Workato with OAuth 2.0 authentication:

RECOMMENDED SETUP

We recommend that you set up a dedicated API user account in Zoom or create a custom OAuth profile to authorize Workato. This allows you to assign the API user to a role with only the necessary permissions.

Alternatively, you can use an existing Zoom owner or admin account if it has the required permissions. Some admin accounts may have restricted access based on their configuration.

Add an API user
View add an API user steps

Complete the following steps to set up a provisioned API user for Workato:

1

Sign into your Zoom account.

2

Go to Admin > User Management > Users.

Add usersAdd users

3

Click Add Users.

4

Enter an appropriate email for the API user. We recommend an IT admin alias.

5

Enter N/A or make selections based on your requirements for the following fields: Department, Manager, Job Title, Location, and User Groups.

6

Click Add.

7

Go to Admin > Roles.

8

Select Add Role.

9

Provide a Role Name and Description.

10

Click Add.

11

Go to Roles > Roles Settings and add the following permissions to your Zoom role. Role permissions are required to allow the Workato Zoom connector to perform account-level actions, such as scheduling meetings or webinars on behalf of other Zoom users.

  • Users: View and Edit
  • Role management: View and Edit
  • Groups: View and Edit
  • Recording management: View and Edit
  • Zoom rooms: View and Edit
  • Meetings: View
  • Webinars: View
  • Usage reports: View
  • Schedule tracking fields: View and Edit
12

Click Save Changes.

13

Go to User Management > Users and locate the user you created in the preceding steps.

14

Click Edit and use the User Role drop-down menu to select the role you created.

15

Click Save.

Create a custom OAuth profile
View create a custom OAuth profile steps

Complete the following steps to create a custom OAuth profile for Workato:

1

Go to Tools > Custom OAuth profiles in Workato.

2

Click + New custom profile.

3

Search for Zoom and select it as your app.

4

Enter a name for your custom OAuth profile in the Name field.

5

Click Create new app.

6

Go to the Zoom App Marketplace and sign in to your Zoom account if you're not signed in already.

7

Click Develop > Build App.

Build appBuild app

8

Choose the kind of app to create from the following options: General App, Server to Server OAuth App, or Webhook Only App. If you can't select the options, you must enable the Zoom for developers role. Refer to the Zoom Select general app features page to learn how to enable the Zoom for developers role.

9

Click Create.

10

Enter a name for your app and select how the app is managed. Refer to the Zoom Step 2: Maintain basic information page for more information.

11

Copy and save the Client ID and Client Secret for use in Workato.

Copy the Client ID and Client SecretCopy the Client ID and Client Secret

12

Enter https://www.workato.com/oauth/callback in the OAuth Redirect URL field.

13

Optional. Configure settings in the Access, Surface, and Embed tabs as required.

14

Go to Scopes and click + Add Scopes to add the required scopes.

15

Search for and select the required scopes for your connection.

16

Click Done.

17

Go to the Local Test tab and select Preview your app listing page to ensure your settings are properly configured.

18

Return to the New custom profile page in Workato and paste the Client ID and Client secret into their respective fields.

Paste the client ID and client secretPaste the client ID and client secret

19

Click Save.

Connect to Zoom with OAuth 2.0 authentication
View connect to Zoom with OAuth 2.0 authentication steps

Complete the following steps to connect to Zoom in Workato:

1

Click Create > Connection.

2

Search for Zoom and select it as your app.

3

Enter a name for your connection in the Connection name field.

Zoom Connection SetupName your connection

4

Optional. Expand the Advanced settings section and use the OAuth 2.0 scopes drop-down menu to specify OAuth scopes to request for your connection.

5

Optional. Use the Custom OAuth profile drop-down menu to select a custom OAuth profile to use for the connection.

6

Click Connect.

7

Sign in to your Zoom account.

Gmail connection setup steps (optional)

View Gmail connection setup steps

REQUIRED PROJECT PROPERTY

Include gmail in the followup_email.enabled_platforms project property to draft and send follow-up emails through Gmail.

Workato supports OAuth 2.0 authentication and Service account authentication for Gmail.

Gmail minimum and default scopes

The See your primary Google Account email address scope is required to establish a connection at a minimum.

Workato requests the following scopes by default if you don't request specific scopes:

  • See your primary Google Account email address
  • See and edit your email labels
  • Send email on your behalf
  • View your email messages and settings
  • Read, compose, and send emails from your Gmail account

Ensure your Google Workspace Admin grants domain-wide authority delegation to your service account if you plan to use a service account to connect to Gmail. This allows it to impersonate the user email entered during connection setup, with the necessary scopes and permissions.

Gmail OAuth 2.0 authentication
View OAuth 2.0 authentication steps

Complete the following steps to set up an OAuth 2.0 connection:

1

Sign in to your Workato account and navigate to the project where you plan to add your Gmail connection.

2

Click Create > Connection (or press C twice), then select Gmail as your connection.

3

Provide a Connection name that uniquely identifies the Gmail connection instance.

4

Click the Authentication type menu and select OAuth 2.0.

5

Optional. Click Advanced settings and select additional OAuth 2.0 scopes. If left blank, the following scopes are requested:

  • See your primary Google Account email address
  • See and edit your email labels
  • Send email on your behalf
  • View your email messages and settings
  • Read, compose, and send emails from your Gmail account
6

Optional. Use the Custom OAuth profile drop-down menu to select a custom OAuth profile for your connection.

7

Click Sign in with Google and sign in to your Google account to complete the setup.

Gmail service account authentication
View Service account authentication steps

A Google service account is a specialized Google account associated with a Google Cloud Project (GCP) that can run API requests on your behalf.

Service accounts provide the following benefits:

  • Continuous operation: Service accounts ensure that operations continue even if individual user permissions change.
  • Dedicated permissions: Service accounts can only access projects that you share with them.
  • Dedicated API quotas: You can manage a service account's API quotas through GCP and request quota increases directly from Google.

Refer to the Google service account documentation to learn more about service accounts.

Getting GCP Project service account emailObtain a GCP Project service account email

Set up a Google service account
View Google service account setup steps

Complete the following steps to set up a Google service account:

1

Create a service account in your GCP project.

2

Go to IAM & Admin > Service accounts. Ensure your dashboard is scoped to the project that contains your service account.

Check the scope of your dashboard.Check the scope of your dashboard.

3

Click the Email of the service account you intend to use.

Click the email of the service account you intend to use.Click the Email of the service account you intend to use.

4

Copy the service account's Email and save it to configure your connection later.

Copy the account's emailCopy the account's Email.

5

Go to the KEYS tab.

6

Generate a private key and download it in JSON format. You can only download the key once.

7

Open the JSON file, then copy the entire private key from -----BEGIN PRIVATE KEY----- to -----END PRIVATE KEY-----\n (inclusive) and save it to configure your connection later.

Connect to a Gmail service account in Workato
View Connect to a service account in Workato steps

Complete the following steps to set up a service account connection:

1

Sign in to your Workato account and navigate to the project where you plan to add your Gmail connection.

2

Click Create > Connection (or press C twice), then select Gmail as your connection.

3

Select the Authentication type drop-down menu.

4

Click Sign in with Google and sign in to your Google account to complete the setup.

Outlook connection setup steps (optional)

View Outlook connection setup steps

REQUIRED PROJECT PROPERTY

Include outlook in the followup_email.enabled_platforms project property to draft and send follow-up emails through Outlook.

The Outlook connector supports the following authentication types:

MICROSOFT MFA ENFORCEMENT

Microsoft is rolling out mandatory multifactor authentication (MFA) gradually to different applications and accounts in phases. This enforcement continues throughout 2025 and beyond. Refer to the Microsoft Mandatory multifactor authentication for Azure and admin portals documentation for more information.

We strongly recommend enabling MFA now for all Microsoft accounts used with Workato to avoid service disruptions from short-notice enforcement changes.

Complete the following steps to maintain uninterrupted service:

1

Enable MFA for your Microsoft organization following the Microsoft MFA setup guide. Refer to Set up multifactor authentication for Microsoft 365 for more information.

2

Reconnect your Microsoft connection in Workato.

3

Complete the OAuth flow with MFA when prompted.

4

Test your recipes to ensure they work with the updated connection.

Authorization code grant authentication (OAuth 2.0)
View authorization code grant authentication steps

This authentication method requires the following value for tenant-specific account types:

  • Tenant ID/Domain
Outlook minimum and default scopes (authorization code grant)
View minimum and default scopes

The Salesforce, Gong, Zoom, Gmail, and Outlook connector requests the following scopes for authorization code grant connections by default. These scopes are necessary to use all of the connector's triggers and actions. Additionally, you must assign these permissions to the Workato app as Delegated permissions in the Azure portal.

  • Mail.Send
  • Mail.ReadWrite
  • Mail.ReadWrite.Shared
  • Calendars.ReadWrite
  • Calendars.ReadWrite.Shared
  • User.Read
  • offline_access

The following minimum scopes are required to establish a connection to Salesforce, Gong, Zoom, Gmail, and Outlook using authorization code grant authentication:

  • User.Read
  • offline_access
Outlook setup for authorization code grant authentication

Complete the following steps to set up Outlook for authorization code grant authentication:

Register the Workato app in the Azure portal
View register the Workato app in the Azure portal steps

Complete the following steps to register the Workato app in the Azure portal:

1

Sign in to the Azure portal.

2

Select App registrations > + New registration.

3

Enter a unique name for the application.

4

Use the Supported account types drop-down menu to select an account type.

5

Select Web from the Select a platform drop-down menu.

6

Use the following URI for the Redirect URI:

html
https://www.workato.com/oauth/callback
7

Select Register.

Assign permissions to your app
View assign permissions to your app steps

Complete the following steps to assign permissions to your app:

1

Go to your newly registered app and select Manage > API permissions.

2

Click + Add a permission and select Microsoft Graph.

3

Add the required permissions as outlined in Minimum and default scopes. Depending on your connection type, you must assign Application or Delegated permissions.

Add permissionsAdd permissions

4

Click Add permissions.

Admin consent is required for specific permissions. Refer to Connect Microsoft Entra ID to the Outlook connector to learn more.

Obtain the Directory (tenant) ID from the Azure portal
View obtain the Directory (tenant) ID from the Azure portal steps

This step is required if you plan to use a tenant-specific account. You can skip this step if you plan to use a common, consumer, or organization account type for your connection.

Complete the following steps to obtain the Directory (tenant) ID from the Azure portal:

1

Go to the Overview > Essentials section.

App detailsApp details

2

Copy and save the Directory (tenant) ID for use in Workato.

Connect to Outlook with authorization code grant authentication
View connect to Outlook with authorization code grant authentication steps

Complete the following steps to set up an authorization code grant connection to Outlook in Workato:

1

Click Create > Connection or press C twice.

2

Search for Outlook and select it as your app.

3

Enter a name for your connection in the Connection name field.

4

Use the Location drop-down menu to select the project where you plan to store the connection.

5

Use the Connection account type drop-down menu to select the type of account you plan to use. The available choices are Common, Tenant-specific, Consumer, and Organization.

6

Use the Authentication type drop-down menu to select Authorization code grant.

7

Optional. The connector requests a set of scopes necessary for all triggers and actions to function properly by default. Go to the Advanced settings section to manually select the permissions instead. The minimum permissions required to establish a connection are User.Read and offline_access. Workato always requests these permissions regardless of the permissions you select. Refer to Minimum and default scopes for more information.

8

Optional. Use the Custom OAuth profile drop-down menu to select a custom OAuth profile for your connection. Refer to Outlook custom OAuth for more information.

9

Click Sign in with Microsoft.

Client credentials-based authentication (OAuth 2.0)
View client credentials-based authentication steps
Outlook minimum and default scopes (client credentials)
View minimum and default scopes

We recommend the following scopes for client credentials connections. These scopes are necessary to use all of this connector's triggers and actions. Additionally, you must assign these permissions to the Workato app as Application permissions in the Azure portal.

  • Calendars.Read
  • Calendars.ReadWrite
  • Contacts.Read
  • Contacts.ReadWrite
  • Mail.Read
  • Mail.ReadWrite
  • Mail.Send

The following minimum scopes are required to establish a connection to Salesforce, Gong, Zoom, Gmail, and Outlook with client credentials-based authentication:

  • Mail.Read
Outlook setup for client credentials-based authentication

Complete the following steps to set up Outlook for client credentials-based authentication:

COMPATIBLE AUTHENTICATION

Client credentials-based authentication is only compatible with tenant-specific connections.

Register the Workato app in the Azure portal
View Register the Workato app in the Azure portal steps

Complete the following steps to register the Workato app in the Azure portal:

1

Sign in to the Azure portal.

2

Select App registrations > + New registration.

3

Enter a unique name for the application.

4

Use the Supported account types drop-down menu to select an account type.

5

Select Web from the Select a platform drop-down menu.

6

Use the following URI for the Redirect URI:

html
https://www.workato.com/oauth/callback
7

Select Register.

Assign permissions to your app
View assign permissions to your app steps

Complete the following steps to assign permissions to your app:

1

Go to your newly registered app and select Manage > API permissions.

2

Click + Add a permission and select Microsoft Graph.

3

Add the required permissions as outlined in Minimum and default scopes. Depending on your connection type, you must assign Application or Delegated permissions.

Add permissionsAdd permissions

4

Click Add permissions.

Admin consent is required for specific permissions. Refer to Connect Microsoft Entra ID to the Outlook connector to learn more.

Generate a client secret
View generate a client secret steps

Complete the following steps to generate a client secret:

1

Go to Manage > Certificates & Secrets > Client secrets.

2

Click + New client secret.

3

Provide a Description for the client secret and specify an Expires date.

4

Click Add.

5

Copy and save the client secret Value—not the Secret ID—for use in Workato.

Copy and save the client secret valueCopy and save the client secret value

Obtain the Application (client) ID, Object ID, and Directory (tenant) ID from the Azure portal
View obtain the Application (client) ID, Object ID, and Directory (tenant) ID from the Azure portal steps

Complete the following steps to obtain the Application ID, Object ID, and Directory (tenant) ID from the Azure portal:

1

Go to the Overview > Essentials section.

App detailsApp details

2

Copy and save the Application (client) ID, Object ID, and Directory (tenant) ID for use in Workato.

Obtain the User ID from the Azure portal
View obtain the User ID from the Azure portal steps

Complete the following steps to obtain the User ID from the Azure portal:

1

Go to Home > Users to obtain the User ID.

UsersSelect users

2

Search for and select the default user you plan to use to perform operations. This user doesn't establish the connection but is required for performing certain operations that an app can't perform. It's also required in picklists to pull user data. For example, the folder picklist populates folders belonging to the default user.

3

Copy and save the User principal name. Use this value as the User ID in Workato.

Connect to Outlook with client credentials-based authentication
View connect to Outlook with client credential-based authentication steps

Complete the following steps to set up a client credentials-based connection to Outlook in Workato:

1

Click Create > Connection or press C twice.

2

Search for Outlook and select it as your app.

3

Enter a name for your connection in the Connection name field.

Client credentials connectionClient credentials connection

4

Use the Location drop-down menu to select the project where you plan to store the connection.

5

Select Tenant specific as the Connection account type. This option is specifically designed for users who belong to a particular organization (tenant).

6

Provide your Tenant ID/Domain. This is the Directory (tenant) ID for your app. Refer to Register an app in Azure for more information.

7

Use the Authentication type drop-down menu to select Client credentials.

8

Supply the User ID, Client ID, and Client secret for your app. Refer to Register an app in Azure for more information.

9

Click Sign in with Microsoft.

Project property configuration

The Post Meeting Actions MCP server supports the following project-level properties to control behavior and defaults:

Project-level propertyDescription
transcript_source.enabled_sourcesSelect which transcript source(s) this deployment retrieves calls from: gong, zoom, or both, in priority order.
summary_template.methodology_labelEnter a human-readable label for your organization's sales methodology, such as MEDDIC/MEDDPICC or Value Selling. This label is used for documentation and LLM phrasing.
summary_template.custom_template_idEnter the field-mapping template ID that maps transcript content to your sales methodology's fields. Workato validates this mapping against your Salesforce fields before launch.
system_of_record.field_mappingMap each summary field to its corresponding Salesforce field or object. Workato validates this mapping against your live schema before launch.
system_of_record.write_content_noteConfigure whether to create a linked ContentNote when the server writes a Salesforce summary. Defaults to false.
kb.enabledConfigure whether to allow knowledge base lookups. The server only queries knowledge bases upon request.
kb.sourceSelect which knowledge base source retrieve_kb_resources reads from: customer_stories, confluence, highspot, google_drive, or sharepoint.
kb.max_resultsEnter the maximum number of resources retrieve_kb_resources returns per request. Defaults to 5, up to a maximum of 10.
followup_email.enabled_platformsSelect one or more follow-up email platforms this deployment sends through: gmail, outlook, or both.
followup_email.recipient_ruleSelect the recipient for follow-up emails: The primary meeting contact, the account's primary contact, or a custom rule.
audit.log_retention_daysEnter how many days to retain audit records. Defaults to 365.
server_limits.max_transcript_charsEnter the maximum number of transcript characters processed in each call. Defaults to 200,000.
server_limits.max_activity_lookback_daysEnter the maximum number of days search_call_activities looks back. Defaults to 90.
server_limits.rate_limit_calls_per_minuteEnter the maximum number of calls this deployment can make each minute. Defaults to 20.
View project-level property configuration steps

Complete the following steps to configure your project-level properties:

1

Sign in to your Workato account and go to Projects.

2

Go to the project that contains your MCP server.

3

Click the Settings tab.

Click the Settings tabClick the Settings tab.

4

Select Project properties.

5

Go to the project property you plan to update and click the Edit (pencil) icon.

6

Go to the Value field and make your changes.

How to use Post Meeting Actions MCP server tools

Refer to the following sections for detailed information on available tools.

TOOL CONFIGURATION

A deployed MCP server only exposes the tools selected by its transcript_source.enabled_sources and followup_email.enabled_platforms project properties. For example, a deployment configured with gong and gmail exposes retrieve_call_transcript_gong and the Gmail follow-up tools, not the Zoom or Outlook variants.

The server follows up through either Gmail or Outlook for each call. It doesn't duplicate follow-ups by sending through both.

find_target_record tool

The find_target_record tool finds the Salesforce Opportunity related to a meeting. Your LLM uses this tool to match a company or account name to a specific Opportunity. The tool uses search_call_activities or a transcript tool to find the company if you don't name it directly.

Try asking:

  • What's the Opportunity for my call with Acme?
  • Which account does this call belong to?
  • Find the record for my call with Acme.

search_call_activities tool

The search_call_activities tool finds Salesforce activity history for logged calls or meetings tied to an account within a date range. Your LLM uses this tool to find calls you reference.

Try asking:

  • Find my last call with Acme.
  • Show me my calls with Acme last month.
  • What calls do I have logged with Acme in the past 30 days?
  • Find the most recent call logged against this Opportunity.

retrieve_call_transcript_gong tool

The retrieve_call_transcript_gong tool retrieves transcript and metadata for a Gong-sourced call by its ID. Your LLM uses this tool to retrieve a transcript after search_call_activities identifies a specific call. The tool resumes any prior progress on the call instead of starting over.

Try asking:

  • Pull the transcript from my Gong call with Acme.
  • Get the Gong recording for this call.
  • Summarize what was said on my last Gong call with Acme.

retrieve_call_transcript_zoom tool

The retrieve_call_transcript_zoom tool retrieves transcript and metadata for a Zoom-sourced call. Your LLM uses this tool to retrieve a transcript after search_call_activities identifies a specific call, or as a fallback when the Gong-sourced tool finds no matching call.

Try asking:

  • Pull the transcript from my Zoom call with Acme.
  • Get the Zoom recording summary for this meeting.
  • What was discussed on my Zoom call with Acme?

generate_meeting_summary tool

The generate_meeting_summary tool produces a summary mapped to the configured sales methodology. Your LLM uses this tool to generate a summary after retrieving a transcript, and only passes a different methodology if you explicitly ask for one.

Try asking:

  • Format my call notes using our sales methodology.
  • Summarize this call using MEDDIC/MEDDPICC.
  • What competitors were mentioned in my call with Acme?
  • Regenerate the summary for this call.

get_salesforce_write_policy tool

The get_salesforce_write_policy tool returns the configured sales methodology and the Salesforce fields allowed for post-meeting writes. Your LLM uses this tool to confirm the configured methodology and fields before generating or writing a summary.

Try asking:

  • What sales methodology is this deployment using?
  • Which Salesforce fields can this write to?
  • Show me the write policy for this deployment.

write_summary_to_system_of_record tool

The write_summary_to_system_of_record tool writes a summary to Salesforce as Opportunity fields and a Task, with an optional linked Note. Your LLM uses this tool to commit a summary after showing you a preview and receiving your confirmation.

Try asking:

  • Update Salesforce based on my call with Acme.
  • Change the next step to "Schedule an executive sponsor call" before you save it.
  • Show me what will be written before you save it.
  • Go ahead and save this summary to Salesforce.

retrieve_kb_resources tool

The retrieve_kb_resources tool retrieves supporting customer stories or product resources. Your LLM uses this tool to pull in supporting resources when you ask for a resourced follow-up. This doesn't retrieve a full call transcript.

Try asking:

  • Find relevant case studies for this call.
  • Pull product resources related to this summary.
  • What customer stories match the objections raised in this call?

search_transcript_chunks tool

The search_transcript_chunks tool retrieves chunked transcript documents for a call, or runs a semantic search across transcript chunks. Your LLM uses this tool to find a specific mention or topic within a call without regenerating the whole summary.

Try asking:

  • Search my call with Acme for any mention of budget.
  • Find where the customer talked about renewal timing in this call.
  • Pull the transcript chunks that mention our top competitor.

draft_followup_email_gmail tool

The draft_followup_email_gmail tool drafts a follow-up email to a prospect through Gmail, optionally with supporting resources. Your LLM uses this tool to draft an email and show you the draft for approval before calling the matching send tool.

Try asking:

  • Draft a follow-up email for my call with Acme.
  • Draft a follow-up in Gmail including relevant case studies.
  • Write a follow-up email to [email protected] about this call.
  • Redraft the follow-up email in a more formal tone.

draft_followup_email_outlook tool

The draft_followup_email_outlook tool drafts a follow-up email to a prospect through Outlook, optionally with supporting resources. Your LLM uses this tool to draft an email and show you the draft for approval before calling the matching send tool.

Try asking:

  • Draft a follow-up email for my call with Acme in Outlook.
  • Write an Outlook follow-up including the case studies you found.
  • Draft a follow-up to [email protected] about this call.
  • Redraft the Outlook follow-up in a more formal tone.

send_followup_email_gmail tool

The send_followup_email_gmail tool sends an approved follow-up email through Gmail. Your LLM uses this tool to send an email you approved. Sends are immediate. This tool doesn't support scheduling.

Try asking:

  • Send the follow-up email.
  • Go ahead and send the Gmail draft.
  • Send this email now that I've approved it.

send_followup_email_outlook tool

The send_followup_email_outlook tool sends an approved follow-up email through Outlook. Your LLM uses this tool to send an email you approved. Sends are immediate. This tool doesn't support scheduling.

Try asking:

  • Send the follow-up email.
  • Go ahead and send the Outlook draft.
  • Send this email now that I've approved it.

list_pending_meetings tool

The list_pending_meetings tool lists meetings being processed by this server. Your LLM uses this tool to surface what you still owe follow-up on, without requiring you to name a specific meeting.

Try asking:

  • What calls do I still owe follow-up on?
  • Show me my pending meetings from the last two weeks.
  • What have I not finished processing yet?

Getting started

View and manage your MCP server tools in the Overview page Tools section. Tool management provides the following capabilities:

TOOLS MUST BE STARTED

Your LLM can only access active tools in your MCP server connector.

Last updated: