Short answer: You can get neverbounce job results in NeverBounce by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the NeverBounce Get NeverBounce Job Results action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Job ID job_id | string | Required | The bulk verification job ID |
Page page | string | Optional | Page number for pagination |
Items Per Page items_per_page | string | Optional | Number of items per page |
{"job_id": "e.g. 280000","page": "1","items_per_page": "10"}
{"query": {"page": 1,"job_id": 280000,"items_per_page": 10},"status": "success","results": [{"data": {"name": "John Doe","email": "john@example.com"},"verification": {"flags": ["has_dns","has_dns_mx"],"result": "valid","suggested_correction": ""}}],"total_pages": 100,"total_results": 1000}
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.