Connecting apps

Agents work in your apps through connections. A connection belongs to one company, and each agent uses only the actions its charter grants, through the same approval rules as everything else. Company admins (and account owners and admins) connect apps; everyone in the company can see what's connected.

Everdeck connects to 100 apps. Each has its own setup guide with the exact steps, fields, scopes and actions.

Find the app

Open Integrations. Connected apps lists what this company has connected, and All apps lists every app Everdeck connects to, by category, with a search box and a Connected only switch. Open an app to see what agents can do there and how to connect it.

Connect with a key or token

Where an app offers an API key or token, that's usually the quickest way.

1. Open the app from Integrations and choose a Way to connect.
2. Follow its setup steps to create the key or token in the app.
3. Select Confirm it’s you: Everdeck asks for your second factor before you type any secret.
4. Fill in the fields, and optionally a Name that tells this connection apart from others to the same app, like "Support inbox".
5. Select Check and connect. Everdeck checks the credentials with the app before saving anything, and saves secrets encrypted. They're never shown again: the connection's page shows only that they're saved.

A company can connect the same app more than once, for example two inboxes.

Your own OAuth app

Some apps connect by signing in, through an OAuth app. Everdeck never uses an OAuth app of its own: you create one in the app you're connecting (the setup guide says how), and Everdeck signs in with it. This keeps the access in your hands, under your own app's name and settings.

The redirect URI

When you create the OAuth app, register this redirect URI with it:

https://everdeck.io/api/oauth/callback

The connect page shows the same address with a Copy button, with the scopes Everdeck asks for. Your own MCP servers and API servers that sign in use their own redirect URIs, shown on their pages: https://everdeck.io/api/mcp-servers/oauth/callback and https://everdeck.io/api/api-servers/oauth/callback.

Save the app's client ID and secret

Save the OAuth app's Client ID and Client secret in Everdeck, either on the connect page or on the OAuth apps page (the button at the top of Integrations):

• This company’s apps are used by this company only.
• The account’s apps are shared by every company that has none of its own. Account owners and admins manage them.

To add one there, select Add an OAuth app, choose the App, who it Belongs to, and fill in the Client ID and Client secret, then select Save OAuth app. Every change to an OAuth app asks you to confirm it's you, since it takes a client secret or changes where one goes.

A few apps sign in at an address you type: the HTTP request connector's token endpoint, a self-hosted GitLab, or Salesforce's My Domain. Their OAuth apps belong to one company and are tied to the Token endpoint they were registered for: Everdeck sends the client secret only there.

Sign in

Back on the connect page, select the button that continues to the app, sign in there and approve the access. You return to the connection's page in Everdeck. If the sign-in didn't finish, the page says why, for example a mistyped client ID or redirect URI, and lets you fix the OAuth app and try again.

Test a connection

Each connection's page shows its status, who it acts as, its fields (secrets only as saved) and its last test, and lists the actions agents can be granted with their risk tiers. Select Test to check it again at any time.

When a connection needs attention

A connection's status is Connected, Waiting for sign-in (saved, but nobody has signed in yet) or Needs attention: the app refused it, say because a key was deleted or a sign-in expired. Agents can't use a connection that needs attention. The people who manage the company's connections are told in the app and by email.

To fix it, open the connection and select Edit to replace a key, or Reconnect to sign in again. Changing a field that decides where the credentials go, like an account's address, asks for the secrets again, and for a connection that signs in, leads to a new sign-in.

Disconnect and revoke

Select Disconnect on the connection's page. Agents stop using it at once and its saved credentials are deleted. This can't be undone; to use the app again, connect it again.

For a connection that signed in, Everdeck also asks the app to revoke the sign-in, where the app offers a way to. Where it doesn't, the app's setup guide says where to remove the access yourself. A key or token you created in an app keeps working there until you delete or rotate it in that app.

Put a connection to work

• Grant actions to agents on each agent's Tools tab. See Agents.
• Start work from an app: some apps can send events, such as a new email or a new order, that become tasks through Intake.
• Sync Jira issues with tasks: see Jira sync.