Pusher

undefined

Detail	Value
Category	Communication
Base URL	https://api-{cluster}.pusher.com/apps/{app_id}
Authentication	API Key
Endpoints	5
Connector key	pusher

Using Pusher in a workflow

1. Go to Connections and click New Connection.
2. Pick Pusher from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Trigger Event
GET	Trigger Batch Events
GET	List Channels
GET	Get Channel Users
GET	Authenticate User

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Trigger Event

Detail	Value
Operation ID	trigger_event_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pusher connection from the Connection dropdown.
3. In the Operation dropdown, select trigger_event_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pusher API reference.

GET

Trigger Batch Events

Detail	Value
Operation ID	trigger_batch_events_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pusher connection from the Connection dropdown.
3. In the Operation dropdown, select trigger_batch_events_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pusher API reference.

GET

List Channels

Detail	Value
Operation ID	list_channels_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pusher connection from the Connection dropdown.
3. In the Operation dropdown, select list_channels_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pusher API reference.

GET

Get Channel Users

Detail	Value
Operation ID	get_channel_users_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pusher connection from the Connection dropdown.
3. In the Operation dropdown, select get_channel_users_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pusher API reference.

GET

Authenticate User

Detail	Value
Operation ID	authenticate_user_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pusher connection from the Connection dropdown.
3. In the Operation dropdown, select authenticate_user_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pusher API reference.