Skip to main content
GET /v1/workflows/blocks returns every block with its specs schema.

API Reference

See the full request/response schema and parameters in the API Reference.

Get available blocks

List every block type the API supports, with its specs schema.
cURL
The response lists the blocks in items. Each entry includes the block’s name (used as block_name when building a workflow) and a specs_schema object describing its configurable fields.

Available blocks

None means the block is not in the Workflow Editor.

Find Email

find_email finds a work email (mode: "PROFESSIONAL") or a personal email (mode: "PERSONAL") for each row. Inputs Skipping rows that already have the email With skip_rows_with_existing_input: true, put the email you already have in one of these columns: Blank, N/A and malformed values count as missing, so the row is looked up. Skipped rows keep their position and input values and get email_status (personal_email_status in PERSONAL mode) set to PROVIDED. In PROFESSIONAL mode the matched work email is also written to email when that column is blank or holds a personal address. Output columns

Verify Phone

verify_phone checks each row’s phone number against the person’s full name. Every row gets all twelve output columns, null when not found. Rows skipped for missing input keep any existing verification values; see Handling Errors. Inputs Output columns

Monitor

monitor starts one monitor over the rows that reach it. It runs once all rows have arrived and returns no rows, so place it last in the workflow. Each workflow run starts its own monitor, which keeps checking on its own schedule after the run ends. Specs Retrieve the monitor a run started with GET /monitors/for-run/{workflow_run_id}/{block_id}. This lookup has no /v1 route yet, so it uses the original route, which keeps working. See Monitor Endpoints.

Pricing

See Credit Costs for more information.