Pusher × AmbactiBring Pusher into
the flow of work.
A little less busywork with Pusher.
Channels6 capabilities+
- Trigger event
Trigger an event on a specified channel.
- List channels
Query for a list of channels within an application that have active subscriptions.
- Get channel information
Retrieve the state of an individual channel by its name.
- Get presence users
Retrieve a list of users present on a presence channel.
- Fetch info for multiple channels
Allows fetching a hash of occupied channels optionally filtered by prefix.
- Fetch info for one channel
Retrieves information about a specific channel.
Events2 capabilities+
- Trigger event
Triggers an event on a specified channel.
- Trigger multiple events
Triggers multiple events on specified channels.
Batch_events1 capabilities+
- Trigger multiple events
Triggers multiple events in a single call (up to 10 per call on the multi-tenant clusters).
Channel1 capabilities+
- Fetch info for one channel
Fetch one or some attributes for a given channel.
Users2 capabilities+
- Terminate user connections
Terminates all connections of a specified user.
- Fetch users
Retrieves a list of users connected to a channel.
Frequently asked
questions.
What could an Ambacti integration do with Pusher?
The documented operations include Channels: Trigger event; Channels: List channels; Channels: Get channel information; Channels: Get presence users.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in Pusher?
Decide which work could run on its own and which steps need your review.