Short answer: Drop the "SendGrid → Get List" 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 |
|---|---|---|---|
List ID list_id | string | Required | The List ID assigned by Sendgrid. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
{"list_id": "{{trigger.list_id}}"}
{"id": "abc-123","name": "My List","contact_count": 42}
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.