HTTP request
Call any HTTP API your company uses, under a base URL you set and with the authentication you choose. Agents read with GET and change data with POST, PUT, PATCH and DELETE.
- Category
- Utilities
- Ways to connect
- 7
- Actions for agents
- 5
- Triggers
- 1
Ways to connect
A company admin connects HTTP request from the Integrations page in Everdeck. Keys, tokens and secrets are encrypted before they're stored, and the connection's Test button checks it works before any agent uses it.
-
Bearer token Token
Copy a key or token from HTTP request and paste it into Everdeck.
-
API key in a header API key
Copy a key or token from HTTP request and paste it into Everdeck.
-
API key in the query string API key
Copy a key or token from HTTP request and paste it into Everdeck.
-
Username and password (HTTP Basic) Username and password
Enter the account details the connect form asks for, with a password or secret from HTTP request.
-
OAuth 2.0 client credentials (no sign-in) Your OAuth app
Create an app of your own with HTTP request and paste its credentials into Everdeck. The connection then works without anyone signing in.
-
OAuth 2.0 with your own app (sign in) Your OAuth app
Create an OAuth app of your own with HTTP request, paste its client ID and secret into Everdeck, then sign in to HTTP request and approve access. Access runs through your own app, never one Everdeck shares with other customers.
-
No authentication No sign-in
No account to sign in to: fill in the settings the connect form asks for.
What agents can do with HTTP request
An agent can only use the actions its charter grants. Each action has a risk tier, and the tier decides whether it runs on its own, asks first or always asks a person.
Runs on its own 1
Looking things up, writing to Everdeck's own records and changes one step can undo. Once an agent's charter grants one of these, it runs without asking, unless you set it to Ask first in the charter or one of your approval rules covers it.
-
GET request Tier 0 · Read Outside content
Read from the API: send a GET to a path under the connection's base URL. Returns the status code, key response headers (content type, location, link, rate limits) and the body: JSON parsed, text trimmed, files saved to the company's files.
Asks first 3
Anything a customer or the public sees. By default a charter grants these as Ask first: the agent sends an approval request and waits for a yes. A company admin can switch one to Auto in the charter after confirming with their second factor. Even then, once an agent has read outside content, such as a customer's email, its tier 3 and 4 actions need a person by default for the rest of that session.
-
POST request Tier 3 · External Outside content
Create something or trigger an action: send a POST with a JSON, form, text or file body. Returns the status, key headers and the response body. Use at most one of json, form or text.
-
PUT request Tier 3 · External Outside content
Replace a resource: send a PUT with a JSON, form, text or file body. Returns the status, key headers and the response body.
-
PATCH request Tier 3 · External Outside content
Change some fields of a resource: send a PATCH, usually with a JSON body. Returns the status, key headers and the response body.
Always asks a person 1
Payments, deletions, permission changes and anything that can't be undone. A person approves every use, and no charter or approval rule can switch that off.
-
DELETE request Tier 4 · Money or irreversible Outside content
Delete a resource with a DELETE request. Returns the status and the response body, if any.
Actions marked Outside content return what people outside your company may have written, such as emails or comments. Agents treat it as information to check, never as instructions.
What can start work
Set a trigger up on the Intake page, and your rules there turn what arrives into tasks for your agents.
-
A GET endpoint you choose (for example /orders?status=new) returned an item that wasn't there before.
Everdeck checks HTTP request every 15 minutes.
Work an agent can take on
Examples for apps in Utilities. What an agent does with HTTP request depends on the actions you grant it.
- Research a question on the web and sum up what it found, with links.
- Pick up work your own systems send to Everdeck by webhook.
- Work with an app that has no integration yet, through its own API.
Set it up
The HTTP request setup guide walks through each way to connect: what to set up first and the fields to fill in, then how to start work from its triggers on the Intake page.
Your company, always on deck.
Start a 14-day trial. Card first, nothing charged until day 14.