Get channel
ReadWhether a channel is occupied, with optional user count, subscription count or cache.
Permissions and limits
Account permissions
- A Pusher Channels app key and secret
Messaging · CONNECTIONPusher + NodeHub
Trigger Pusher Channels events (one or a batch), read occupied channels and presence users, and terminate a user's connections.
Explore 6 workflow actions for Pusher, including account permissions and operation limits.
3 read actions3 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
List channels
ReadThe occupied channels, optionally by name prefix, with optional attributes.
Permissions and limits
Account permissions
- A Pusher Channels app key and secret
List presence channel users
ReadThe IDs of the users subscribed to a presence channel.
Permissions and limits
Account permissions
- A Pusher Channels app key and secret
Terminate user connections
WriteClose every connection a user has (they may reconnect).
Permissions and limits
Account permissions
- A Pusher Channels app key and secret
A repeated request may repeat the external action. Review the previous result before retrying a write.
Trigger batch events
WriteSend several events in one call (up to 10 on the multi-tenant clusters); each has name, data, channel and optional socket_id and info.
Permissions and limits
Account permissions
- A Pusher Channels app key and secret
A repeated request may repeat the external action. Review the previous result before retrying a write.
Trigger event
WriteSend an event to one or more channels (data at most 10 KB); with info, the answer has each channel's counts.
Permissions and limits
Account permissions
- A Pusher Channels app key and secret
A repeated request may repeat the external action. Review the previous result before retrying a write.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in Pusher. A saved workflow is not a completed provider action.
EXPLORE YOUR STACK
