Skip to content

Verify email addresses in Make scenarios

Integration Automation

Call the PricklyMails API from Make's HTTP app: verify the address a webhook brings in one request, or a whole list as a batch over two scenarios.

No PricklyMails node to install: Make's own HTTP request calls the PricklyMails API, with your key kept as a credential.

Verify for free

Step by step

Verify addresses from Make in four steps

  1. In PricklyMails

    Create an API key in PricklyMails

    1. In the dashboard, open API Keys and click New key.
    2. Under Environment, pick Test first: the key starts with pm_test_, answers from canned results, bills nothing and contacts no mail server.
    3. Copy the key as soon as it shows: it is shown only once.

    Tip

    The Free plan holds one key: once everything works, revoke the test key, then create the one under Live.

  2. In Make

    Save your PricklyMails key as a Make key

    1. In a Make a request module of the HTTP app, set Authentication type to API key.
    2. Next to Credentials, click Add.
    3. Enter a Name, then Bearer pm_live_your_key as the Key: Make sends it as typed, so Bearer and a space come first.
    4. Set API key placement to In the header and API key parameter name to Authorization, then save.

    Warning

    Leave the key out of Headers: Make's HTTP app asks for credentials in their own field, and a value typed in Headers travels with the scenario's blueprint.

    SourceMake's official help center
  3. In Make

    Verify one address in a Make scenario

    One request returns the result: with Prefer: wait=12, the response holds it whenever the check ends within 12 seconds, and is a 202 without it otherwise.

    1. After the module that brings the address, such as a Custom webhook, add a Make a request module with your key.
    2. Set URL to https://api.pricklymails.com/api/verify and Method to POST.
    3. Under Headers, add Prefer, with wait=12 as its value.
    4. Set Body content type to application/JSON and Body input method to JSON string, then paste the body below into Body content.
    5. Replace 1.email in the body with the mapped item that holds the address.
    6. Set Parse response to Yes, and Timeout, in the advanced settings, to 16 seconds.
    7. Add a filter after the module that lets through the bundles whose recommendation is remove.
    body.json
    {
    "email": "{{1.email}}"
}
    SourceMake's official help center
  4. In Make

    Verify a list in Make scenarios

    A Make scenario runs from its first module to its last without looping back, so a batch takes two scenarios: one sends it, a second reads it later.

    1. In the first scenario, gather the contacts with an Array aggregator, then build emails and custom_ids from it with the map() function.
    2. Send them with a Make a request module, POST to https://api.pricklymails.com/api/batches, with your key.
    3. Keep the response's batch_uuid in a Data store.
    4. Schedule the second scenario a few minutes later, and have it read the batch_uuid from the data store.
    5. Read the results with a Make a request module whose Pagination type is Offset-based, with results as the Items path.
    6. Turn the rows into one bundle each with an Iterator, then update each contact by its custom_id with the tool's own module.
    The PricklyMails requests of a batch, one by one
    SourceMake's official help center

Frequently asked questions

Does a blueprint hold my PricklyMails key?

Make's help says a blueprint holds a scenario's modules, their settings and mapped values, and that whoever imports it still creates the connections. Keep the key in the module's credentials, never typed in Headers: a header is part of the module's settings.

SourceMake's official help center

Can Make keep the addresses out of its logs?

Turn on Keep data confidential in the scenario settings, so Make does not store the data a run handled. A webhook still holds the data it receives in its queue until the scenario processes it.

SourceMake's official help center

What if PricklyMails does not answer in time?

Add an error handler to the Make a request module: Skip drops the bundle and goes on with the next one, and Resume goes on with an output you set, such as an empty recommendation.

SourceMake's official help center

Is there a PricklyMails node for Make?

No, and it takes none: Make's own HTTP request calls the PricklyMails API, with the key you saved as a credential.

These trademarks belong to their respective owners. Naming them implies no partnership.

Check your list before your next send.

1,000 tokens free when you sign up, no credit card. After that, you only pay for answers.

Verify for free See pricing