Workflow · version 1.0

React when a list verification job finishes

Receive a signed webhook when a file job completes or fails, check the signature, then fetch the results.

Starts when: ValidReach sends a file.completed or file.failed webhook to your HTTPS endpoint.

Steps

  1. 1. Receive webhook (trigger)

    Read the raw body and the X-Webhook-Timestamp and X-Webhook-Signature headers.

  2. 2. Check signature (branch)

    Compute sha256=HMAC(secret, timestamp.rawBody) and compare.

  3. 3. Download results (http)

    GET the results URL from the payload with your API key.

  4. 4. Store or notify (action)

    Save the file or notify your team.

  5. 5. Reject request (action)

    Return an error and ignore the payload.

  6. 6. Alert on failure (action)

    For file.failed, notify someone to look at the job.

Connections

  • Receive webhook → Check signature
  • Check signature → Download results (signature valid, file.completed)
  • Check signature → Alert on failure (signature valid, file.failed)
  • Check signature → Reject request (signature invalid)
  • Download results → Store or notify

Credentials you provide

  • ValidReach API key YOUR_API_KEY: Create it under Settings → API keys and store it in your automation tool’s secret storage.
  • Webhook secret YOUR_WEBHOOK_SECRET: Returned when you register the webhook. Keep it private.

Sample

GET https://validreach.dev/api/v1/verify/file/{taskId}/results
Authorization: Bearer YOUR_API_KEY
Results are returned as CSV by default, or as JSON.

Before you run it

Check the signature against the raw body before parsing it, and reject old timestamps. Test with a small file of addresses you own.

Verification status. Schema: checked in unit tests. Import: not tested on any platform. Sandbox run: not run. The download is this ValidReach definition, not an importable file for an automation platform.