List Batch Checks
mailcheck.list_operations
ActionEmailconnection required
Calls the Mailcheck API with the connection's credentials.
List the batch checks started on this Mailcheck account.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Mailcheck
- Secret shape
- the API key, or {"api_key": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
page_size How many operations to return in this page. | number | No | — | ≥ 1 | — |
page_token The next_page_token from a previous call, to fetch the following page. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
operations The batch checks, each flattened as above. | array | — |
count How many operations this page carried. | number | — |
next_page_token Token to pass back as page_token for the next page; empty on the last. | string | — |
{
"count": 0,
"next_page_token": "",
"operations": []
}Related Mailcheck nodes
See List Batch Checks run in a workflow.
In a technical demo we add the Mailcheck connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.