Integrations
Push results to the channel where decisions get made
One-way, and that is usually right: a notification that can also change state turns a chat room into an admin panel.
Read from the systems that already hold your records
Two-way if you write back, and that is the connection to document most carefully.
Fill this in: replace the two cards above with the integrations Fotoslov — переводчик по фото really ships, and add one card per integration. An integration page that lists something you have not built is the most expensive kind of wrong.
Connect over the API#
Where no first-party integration exists, the API is the answer. Show the same call in the shapes your readers use.
Both variants send the same request and get the same response back.
curl -X POST "https://api.example.com/v1/events" \
-H "Authorization: Bearer $API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"type": "report.ready", "project": "first-project"}'await fetch("https://api.example.com/v1/events", {
method: "POST",
headers: {
Authorization: "Bearer " + process.env.API_TOKEN,
"Content-Type": "application/json",
},
body: JSON.stringify({ type: "report.ready", project: "first-project" }),
})What to write about each integration#
Four things, and most integration pages skip the last two: what it does, how to connect it, what happens when the other side is unavailable, and how to disconnect it cleanly. The last one matters because somebody eventually has to, usually in a hurry.