Clarify which Buildkite account is connected to an Algolia incident
During an incident, it helps to know which Buildkite user the connected token belongs to. Send the Algolia incident context to a Notis Webhook and get the current authenticated user details in the report.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get User
Retrieves details about the authenticated user who owns the API token.
Why this helps
Incident responders can lose time figuring out which account a connected Buildkite token represents while they are already tracking Algolia context.
- See the current authenticated Buildkite user details alongside incident context.
- Help responders identify the account associated with the connected API token.
- Keep the report focused on identity lookup without implying access changes or incident remediation.
Setup
Build it in a few focused steps.
- 1Connect Algolia and Buildkite once in the Notis portal.
- 2Create an automation from any channel or in Automations, New Automation. Give it a name and choose a report channel.
- 3Tell Notis: When an incident request arrives with Algolia context, retrieve details about the current authenticated Buildkite user and report them alongside the request. Do not make account or incident changes.
- 4Pick the Webhook trigger and choose where run reports go.
- 5Send one real incident request and verify the user details match the connected Buildkite account.
Questions about this workflow
Does the workflow identify the person who submitted the incident request?
No. It retrieves the current authenticated Buildkite user, the account associated with the connected API token.
Will it resolve or update the incident?
No. The available action retrieves user details; it does not change Buildkite or Algolia data.
What if the incident request has no Algolia context?
Notis can still retrieve the authenticated Buildkite user, but the report should state that the request context was missing.
When this happens · Trigger
Do this · Action
Retrieves details about the authenticated user who owns the API token.
Supported Triggers and Actions
Notis builds workflows that link Algolia to Buildkite. A trigger fires from one place; an action lands in another.
Algolia triggers
Buildkite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current Access Token
Retrieves details about the current authenticated access token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Meta
Retrieves API metadata, including webhook IP addresses.
List Pipeline Agents
Lists connected agents for an organization.
Get User
Retrieves details about the authenticated user who owns the API token.
List Organizations
Lists organizations available to the current API token; organizations without an active plan are omitted.
Connect any two apps with Notis in the middle.
Algolia and Buildkite, or any other combination from 1,600+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Buildkite.