# Redis message - Workflow trigger | Docs - nodulz

Source: https://nodulz.com/docs/nodes/redis_trigger

Language: en

Triggers the workflow for each Pub/Sub message received on a Redis channel.

## Usage and specifics

Select the Redis connection, mode and channels or filters. Publish to activate listening. Key notifications require the corresponding Redis server configuration.

Technical type : `redis_trigger`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Create and configure the credential : redis](/docs/credentials/redis)

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `credentialId` | `string` | `""` | - |
| `channel` | `string` | `""` | - |
| `testPayload` | `string` | `""` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `credentialId`<br>Redis credential | Select a Redis vector credential with a redis:// or rediss:// URL and optional password. |
| `channel`<br>Channel | Exact Pub/Sub channel. Listens after publication. Messages sent while disconnected are lost, with no replay. |
| `testPayload`<br>Test data (JSON) | JSON object simulating the received message. The message field contains the raw published text. |

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "credentialId": "",
  "channel": "",
  "testPayload": ""
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)