Short answer: Drop the "NeverBounce → List NeverBounce Jobs" 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 |
|---|---|---|---|
Page page | string | Optional | Page number for pagination |
Items Per Page items_per_page | string | Optional | Number of items per page |
{"page": "1","items_per_page": "10"}
{"query": {"page": 1,"items_per_page": 10},"status": "success","results": [{"id": 280000,"total": {"records": 1000,"billable": 980,"processed": 1000},"filename": "contacts.csv","created_at": "2025-03-10 10:00:00","job_status": "complete","finished_at": "2025-03-10 10:05:00"}],"total_pages": 1,"total_results": 5}
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.