Short answer: Drop the "Zendesk → List Groups" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Per Page per_page | string | Optional | Results per page (max 100) |
Page page | string | Optional | Page. e.g. "1" |
{"per_page": "100","page": "1"}
{"count": 2,"groups": [{"id": 101,"name": "Support","default": true,"created_at": "2024-01-01T00:00:00Z"},{"id": 102,"name": "Billing","default": false,"created_at": "2024-01-02T00:00:00Z"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.