Skip to content
Notis

Confirm which Buildkite account your review request uses

A quick account check can clarify whose Buildkite credentials are in use before you pass an engineering follow-up along.

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

Multiple work accounts can make it unclear which Buildkite identity a follow-up will use, especially when switching from marketing analysis.

  • Identify the current authenticated Buildkite user.
  • Reduce confusion when several Buildkite accounts are in use.
  • Keep account verification tied to an intentional webhook request.

Setup

Build it in a few focused steps.

  • 1Connect Adyntel and Buildkite once in the Notis portal.
  • 2Create an automation that asks Notis to retrieve the current Buildkite user details.
  • 3Pick a webhook trigger that starts with an HTTP request.
  • 4Choose where Notis should send run reports.
  • 5Test the automation with one real review follow-up.

Questions about this workflow

Does the action reveal the secret token value?

The action retrieves details about the current authenticated user. It is intended to identify the account that owns the token.

Can this verify token scopes?

No. Use the separate Get Current Access Token action to confirm token validity and scopes.

Does this run whenever Adyntel data changes?

No. Adyntel has no listed trigger events, so the workflow starts from a Notis webhook request.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Adyntel to Buildkite. A trigger fires from one place; an action lands in another.

Adyntel triggers

Buildkite actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Current Access Token

Retrieves details about the current authenticated access token.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get Meta

Retrieves API metadata, including webhook IP addresses.

ActionInstant

List Pipeline Agents

Lists connected agents for an organization.

ActionInstant

Get User

Retrieves details about the authenticated user who owns the API token.

ActionInstant

List Organizations

Lists all organizations the authenticated user belongs to.

ActionInstant

Connect any two apps with Notis in the middle.

Adyntel and Buildkite, or any other combination from 1,000+ 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.