Skip to content
Notis

Check Slack availability for a Chatwork handoff

Before you route a Chatwork follow-up, check the intended Slack user's current presence and use that signal to plan your next step.

Trigger

Webhook received

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

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

A handoff can lose momentum when you message someone who is away, and checking presence adds another manual step to an already busy workflow.

  • Add a current availability signal to handoff planning
  • Avoid an extra manual Slack check
  • Help choose a sensible follow-up moment

Setup

Build it in a few focused steps.

  • 1Connect Chatwork and Slack once in Notis.
  • 2Create an automation in plain language or in Automations, New Automation.
  • 3Describe the outcome: use the requested Slack user identifier from a Chatwork handoff request to retrieve their current presence and report the result.
  • 4Pick a Notis webhook trigger and choose where run reports should go.
  • 5Test with one real Slack user and a Chatwork handoff request.

Questions about this workflow

Does this show someone's historical availability?

No. Slack's presence action returns a current real-time status, not historical presence or a reason.

What starts the presence check?

An HTTP request to the Notis webhook starts it. Chatwork has no listed event trigger here.

Can Notis infer who the handoff is for?

Only if the request or available Chatwork context identifies the Slack user clearly. The workflow should report when that information is missing.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Chatwork triggers

Slack actions

Recurring trigger

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

TriggerScheduled

Set snooze duration

Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.

ActionInstant

Webhook trigger

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

TriggerInstant

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.

ActionInstant

Add an emoji alias

Adds an alias for an existing custom emoji in a slack enterprise grid organization.

ActionInstant

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.

ActionInstant

Add a star to an item

Stars a channel, file, file comment, or a specific message in slack.

ActionInstant

Add call participants

Registers new participants added to a slack call.

ActionInstant

Add emoji

Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Chatwork 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.