A connector is a link between ScriptRunner Connect and a third-party service that ScriptRunner Connect manages on your behalf.

You can set up connectors without being in a workspace; these connectors become global. You can then associate global connectors to multiple workspaces (creating API connections) and apply different configurations for different workspaces.

More to come  😊

Additional connectors will be added throughout beta testing as they are ready to test. 

Want a specific connector added to ScriptRunner Connect? Contact us!

Available ScriptRunner Connect Connectors

ScriptRunner Connect is equipped with connectors for the following apps and services:

ConnectorAppAuth TypeEvent Listeners
Bitbucket CloudOAuth 2.0(tick)
Bitbucket On-PremiseOAuth(tick)
Confluence CloudOAuth 2.0(error) 1
Confluence On-PremiseOAuth(tick)
GitHubOAuth 2.0(tick)
GitLabOAuth 2.0(tick)
Google CalendarOAuth 2.0(error) 2
Google SheetsOAuth 2.0(error) 2
Jira CloudOAuth 2.0(tick)
Jira On-PremiseJira On-PremiseOAuth(tick)
Jira Service Management On-Premise(tick)
Jira Service Management On-Premise Assets(error)
Tempo Timesheets On-Premise(error)
Tempo Planner On-Premise(error)
Jira Service Management CloudOAuth 2.0(tick) 3
Jira Service Management Cloud AssetsBasic (API Token)(error)
MicrosoftTeamsOAuth 2.0(tick)
monday.comOAuth 2.0(tick)
OpsgenieBasic (API Token)(tick)
SalesforceOAuth 2.0(tick)
ServiceNowOAuth 2.0(tick)
SlackApp credentials(tick)
StatuspageBasic (API Token)(tick)
Tempo CloudOAuth 2.0(error)
TrelloBasic (API Token)(error) 4
ZoomApp credentials(tick)

Confluence Cloud officially does not support webhooks. As a workaround, you should be able to use a third-party add-on to register a webhook using the generic event listener in ScriptRunner Connect. Alternatively, you can also use ScriptRunner for Confluence Cloud to set up an event listener in Confluence and call a Generic Event Listener in ScriptRunner Connect whenever the event gets fired.

Here is an example of how you would go about writing a Groovy script in ScriptRunner that calls a Generic Event Listener HTTP endpoint in ScriptRunner Connect. This example demonstrates how to listen to the Label Added event by extracting a couple of event properties and then sending them to ScriptRunner Connect as part of the HTTP body:

def pageTitle = labeled.asType(Map).title def pageId = labeled.asType(Map).id def labelTitle = label.asType(Map).title"Page Title: ${pageTitle}")"Page ID: ${pageId}")"Label Title: ${labelTitle}") def response = post("GENERIC_HTTP_ENDPOINT_URL") .body( confPageTitle: pageTitle, confPageId: pageId, labelTitle: labelTitle) .asObject(Map)

2 Google products don't support webhooks, but as a workaround, you can write a Google Apps Script that triggers for events you are interested in, which, in turn, calls the generic event listener to listen for events on the ScriptRunner Connect side.

3 For the most part, Jira Service Management Cloud reuses base Jira event types.

4 At this time, Trello webhooks are not supported, but you can use Trello's API to set up webhooks. Here is a template that demonstrates this use case.

Generic API Connector

There's also a generic API connector and generic event listener you can use to connect and listen to events from unlisted apps and services.

You can also use basic/fixed authentication for most services instead of using OAuth. To use fixed authentication, create a generic API connection and either construct the Managed API manually for the generic API connection or use the Fetch API directly.

Creating a Connector

Making new connectors is easy. Follow these steps!

  1. Click Connectors on the left side of the page.
    The Connectors view opens in the app.

  2. Click Create New.

    The Select App for Connector screen appears.

  3. Select one of the connector options.
    The Manage Connector dialog appears.

  4. Enter a name for the connector, then click Authorize.

    The authorization wizard appears. (Authorization steps vary from app to app.)

  5. Complete the authorization steps in the wizard to authorize the connector.
    This includes a permissions prompt that, when accepted, allows ScriptRunner Connect to work with your selected app.

    Here's an example from the Google Calendar authorization, for which you should click Allow:

  6. Once the authorization steps are complete, click Save on the Manage Connector dialog.

    A success message appears in the app, and your new connector is created.

Deleting a Connector

To delete a connector, click the ellipsis icon, then Delete.

On this page