Connector functions

Connectors are step functions for workflows that behave like Slack functions for services external to Slack. They take inputs and perform work for you when added as steps to your workflows.

Browse connectors

Authentication

Connectors use either OAuth or workspace environment variables to handle authentication.

Most connectors rely on one of two OAuth strategies: End-user and Developer. These connectors reply on an access token input parameter that you as a developer configure while adding the connector as a step in a workflow.

End-user authentication

The first authentication strategy is called END_USER. This strategy is supported by most connectors.

// An example access token property for a Salesforce connector:
salesforce_access_token: {
    credential_source: "END_USER"
}

When a connector's access token credential source is set to END_USER, the auth token of the user who started the workflow will be used in the connector step.

In cases like this, when a user starts a workflow from a shortcut link, the user will be prompted to connect their third-party service account via an OAuth flow. All of this— except for when they are sent to a browser to complete the authentication flow—happens inside their Slack client.

You do not need to do anything else besides set the credential_source to END_USER to configure end-user authentication for a connector.

Developer authentication

The second authentication strategy is DEVELOPER. This strategy is not supported by all connectors.

// An example access token property for a Salesforce connector:
salesforce_access_token: {
    credential_source: "DEVELOPER"
}

When a connector's access token credential source is set to DEVELOPER, the auth token that an app collaborator configured as part of a CLI-initiated OAuth flow before deploying the app will be used.

In cases like this, when a user starts a workflow from a shortcut link, the user is not prompted to connect any third-party service account. Instead, the connector step will run using the auth token configured by one of the app's collaborators.

In addition to setting the credential_source to DEVELOPER, you'll also need to define an OAuth2 provider and then configure external authentication for your app. You can do this by following the steps in the External auth guide.

Workspace environment variable authentication

Connectors that rely on workspace environment variables to handle authentication will require workspace admins to set these up before the connector can be used in a workflow.

Admins can set workspace environment variables for connectors that require them from within Workflow Builder, in the Manage Integrations section.

To open the Manage Integrations section, open Workflow Builder and access the additional options menu to the right of the Create Workflow button.

Building your own connectors

Creating your own connectors opens many more interoperability possibilities. We're not quite ready to enable developers to build their own connectors, but we'd love to hear from you if you're interested and patient.

In the meantime, we recommend building custom functions that call APIs with external authentication.