Check Slack presence before Buildkite follow-up
Add a current presence check to a recurring pipeline or deployment follow-up review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Retrieve user presence
Retrieves a slack user's current real-time presence (e.g., 'active', 'away') to determine their availability, noting this action does not provide historical data or status reasons.
Why this helps
Deciding whether to follow up now or later can involve unnecessary back and forth across tools.
- Retrieve real-time Slack presence for a known user.
- Include current active or away context in a run report.
- Support more considered follow-up timing.
Setup
Build it in a few focused steps.
- 1Connect Buildkite and Slack once in the Notis portal.
- 2Create an automation from Automations, New Automation, or by telling Notis what to do in plain language.
- 3In one instruction, ask Notis to check current presence for a known user relevant to the Buildkite follow-up.
- 4Pick a recurring schedule as the trigger and choose where run reports should go.
- 5Test with one real follow-up and confirm the presence result is current and correctly matched.
Questions about this workflow
Does Slack presence show historical status?
No. The action reports real-time presence such as active or away, without historical data or status reasons.
Can the workflow infer who owns a Buildkite task?
Only if the available context identifies the person. Supply a known Slack user when Buildkite context does not identify one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Buildkite to Slack. A trigger fires from one place; an action lands in another.
Buildkite triggers
Slack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Set snooze duration
Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a custom emoji to a Slack team
Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.
Add an emoji alias
Adds an alias for an existing custom emoji in a slack enterprise grid organization.
Add a remote file
Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.
Add a star to an item
Stars a channel, file, file comment, or a specific message in slack.
Add call participants
Registers new participants added to a slack call.
Add emoji
Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.
Add reaction to message
Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.
Connect any two apps with Notis in the middle.
Buildkite and Slack, 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 Slack.