Skip to content
Notis

See where collaborators are present as projects start

Review current channel participation as soon as a new Jira project is created.

Trigger

New Project

Triggered when a new project is added in Jira

Action

Query Batch Presence

This tool enables querying the presence states of multiple channels in a single api request. the api retrieves the member presence details of the specified channels in parallel.

Why this helps

Project setup can stall while you work out which collaborators are active in the relevant channels.

  • Check presence across multiple channels in one request.
  • Include current activity context in a project run report.
  • Reduce manual searches for active collaborators.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Ably once in the Notis portal.
  • 2Create an automation in Automations, then New Automation, and name it.
  • 3Tell Notis which Ably channels to query when a Jira project is added and ask it to summarize presence.
  • 4Pick the Jira New Project trigger.
  • 5Choose a report channel and test with one real project example.

Questions about this workflow

Does this query one or many channels?

The action can query member presence details for multiple specified channels in parallel.

Can it tell who will be available later?

No. It returns presence states at query time and does not predict future availability.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Ably actions

Recurring trigger

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

TriggerScheduled

Query Batch Presence

This tool enables querying the presence states of multiple channels in a single api request. the api retrieves the member presence details of the specified channels in parallel.

ActionInstant

Webhook trigger

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

TriggerInstant

Query Batch Presence History

This tool enables querying presence history for multiple channels in a single api request. it uses the get endpoint at https://rest.ably.io/presence to retrieve the member presence history details of the specified channels in parallel.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Create Ably Channel

Creates a new channel or retrieves an existing channel in ably. this tool allows you to programmatically create and initialize channels for real-time messaging. since ably creates channels implicitly when first used, this action publishes an empty initialization message to create/activate the channel.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Delete Channel Subscription

This tool allows you to unsubscribe devices or clients from push notifications for specific channels. the operation is asynchronous, so immediate requests after deletion may briefly still return the subscription.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Get Channel Details

This tool retrieves metadata and details for a specific channel in ably. it returns a channeldetails object containing information about the channel's status, occupancy, and other metadata. the endpoint provides visibility into channel activity, including metrics such as connections, presence, publishers, and subscribers, and requires appropriate permissions.

ActionInstant

Get Channel History

This tool retrieves the message history for a specified ably channel. it uses the get /channels/{channelid}/messages endpoint to return a paginated list of messages in chronological order, subject to parameters such as 'channelid', 'limit', 'direction', 'start', and 'end'. the tool is useful for auditing, recovering missed messages, analyzing channel activity, and debugging message flows. authentication is required via basic or token authentication.

ActionInstant

Get Channel Presence History

This tool retrieves the history of presence messages for a specified channel in ably. it allows you to query presence events on a channel within a given time period.

ActionInstant

Get Ably Service Time

This tool retrieves the current server time from ably's service in milliseconds since the epoch. it is particularly useful for time synchronization and generating valid tokenrequest timestamps to prevent replay attacks. the endpoint supports multiple content types, handles http errors, network issues, and is a fundamental tool for ensuring accurate timing in ably applications.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Ably, 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 Ably.