Integration · Developer
AI agents for Pusher Channels
Send realtime events to the browsers and phones subscribed to your Pusher Channels app, one event to up to 100 channels or a batch of up to 10 different events at once, and see which channels are in use.
- Actions
- 5
- Read
- 3
- Write
- 2
Actions
What your agents can do in Pusher Channels
Send realtime events to the browsers and phones subscribed to your Pusher Channels app, one event to up to 100 channels or a batch of up to 10 different events at once, and see which channels are in use, how many people are subscribed and who is in a presence channel. Use it to push a live update (a new message, a status change, a finished job) to an app's users without them refreshing.
Read 3
Look things up. Nothing changes.
List channels in use
Lists the channels that have at least one subscriber, as a channels object keyed by channel name.
Get a channel
Says whether a channel is occupied (has subscribers) and, when asked, its user_count (presence channels) or subscription_count (other channels, once subscription counting is on in the app's settings).
List who is in a presence channel
Lists the users subscribed to a presence channel (its name starts with presence-), at users, each with the id your app gave them when they joined.
Write 2
Create, change or send.
Send an event
Sends one event to one or more channels (up to 100).
Send a batch of events
Sends up to 10 events in one call, each to its own channel with its own name and data (at most 10 KB each).
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details Pusher Channels gives you for its API.
What you enter
- Key
- Secret
Settings
- App ID
- Cluster
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Pusher Channels data
Ask a question in plain words. The agent can list channels in use, get a channel or list who is in a presence channel in Pusher Channels, then answers with what it found.
- 02
Let an agent update Pusher Channels
Have the agent send an event or send a batch of events in Pusher Channels as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Pusher Channels and Slack: it can list channels in use in Pusher Channels and post a summary to a Slack channel in the same run.
Works well with
More Developer tools
- GitHub4 actionsOpen and comment on issues, and start GitHub Actions workflows, in the repositories a personal access token can reach.
- GitLab4 actionsOpen and comment on issues, and start CI/CD pipelines, in the GitLab.com projects an access token can reach.
- Bitbucket3 actionsComment on and read pull requests, and start Bitbucket Pipelines, in the Bitbucket Cloud repositories your Atlassian API token can reach.
- Sentry3 actionsList, read, resolve and ignore error issues in a sentry.io organization, in its US or EU (Germany) data region.
- Datadog2 actionsPost events to the Datadog Event Explorer and send custom metric points, on any Datadog site, with an API key.
- PagerDuty4 actionsOpen, acknowledge and resolve PagerDuty incidents, add notes to them, and see who is on call for a schedule.
FAQ
Pusher Channels and MyDeepAgents
Can MyDeepAgents connect to Pusher Channels?
Yes. The Pusher Channels connector has 5 actions: 3 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Pusher Channels?
Enter the sign-in details Pusher Channels gives you for its API. You'll need: Key and Secret. The connection also asks for: App ID and Cluster. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Pusher Channels without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.
Can I use Pusher Channels in workflows as well as agents?
Yes. Every Pusher Channels action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Pusher Channels to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.