Artisan IMG > Hunter (hunter) (7795123c-8b57-422b-a673-6489ff6b229d)
Artisan IMG > Hunter (hunter) (7795123c-8b57-422b-a673-6489ff6b229d)


Hunter is a search platform to find and verify professional email addresses.


Hunter helps any individual or business looking to build a database of professional contact information associated with any domain. Hunter focuses on finding professional email addresses. It is ideal for companies that would like to verify email addresses used and cold outreach to send highly personalized cold emails on autopilot to fill their pipeline.

API INFO: The Base URL used for the hunter connector is More information can be found on their main API documentation (v2) site.


Within the workflow builder, highlight the Hunter connector.

In the Hunter connector properties panel to the right of the builder, click on the Authenticate tab and the 'New authentication' button.

This will result in a authentication pop-up modal. The first page will ask you to name your authentication and select the type of authentication you wish to create ('Personal' or 'Organisational').

The next page asks you for your 'API Key' credentials.

In order to get this field, head to the Hunter dashboard. Click your profile icon in the top right-hand corner, and select 'API'.

Once you have added these fields to your authentication popup window, click the 'Create authentication' button.

Go back to your settings authentication field (within the workflow builder properties panel), and select the recently added authentication from the dropdown options now available.

Your connector authentication setup should now be complete.

Available Operations

The examples below show one or two of the available connector operations in use.

Please see the Full Operations Reference at the end of this page for details on all available operations for this connector.

Using the Raw HTTP Request ('Universal Operation')

As of version 2.0, you can effectively create your own operations.

This is a very powerful feature that you can use when there is an endpoint in Hunter that is not used by any of our operations.

To use this you will first of all need to research the endpoint in the Hunter API documentation v2, to find the exact format that Hunter will be expecting the endpoint to be passed in.

Note that you will only need to add the suffix to the endpoint, as the base URL will be automatically set (the base URL is picked up from the value you entered when you created your authentication).

The base URL for Hunter is:

For example, say that the 'List leads lists' operation did not exist in our Hunter connector, and you wanted to use this endpoint. You would use the Hunter API docs to find the relevant endpoint - which in this case is a GET request called: /leads_lists.

More details about this endpoint can be found here.

As you can see, there is also the option to include a query parameter, should you wish to do so. So if you know what your method, endpoint and details of your query parameters are, you can get the leads lists information with the following settings:

Method: GET

Endpoint: leads_lists

Query Parameter:

  • Key: offset Value: 0

  • Key: limit Value: 10

Body Type : none : { "none" : null }

Final outcome being:

Example Usage

TRAY POTENTIAL: is extremely flexible. By design there is no fixed way of working with it - you can pull whatever data you need from other services and work with it using our core and helper connectors. This demo which follows shows only one possible way of working with and the hunter connector. Once you've finished working through this example please see our Introduction to working with data and jsonpaths page and Data Guide for more details.

Below is an example of a way in which you could potentially use the Hunter connector, to retrieve the details of a lead.

The steps will be as follows:

  1. Setup using a manual trigger and list all the leads.

  2. Loop through the received list of leads.

  3. Retrieve the details of each lead.

Your completed workflow should look similar to this:

1 - Setup Trigger & List leads

With your Manual trigger in place, add a Hunter connector. Set the operation to 'List leads'.

Feel free to re-name your steps as you go along to make things clearer for yourself and other users. The operation names themselves often suffice.

Upon completion, you will have set up the manual trigger and fetched a list of all the leads in your account.

2 - Loop collection

Next, search for the Loop connector within your connector panel, and drag it into your workflow as your next step. Set your operation to 'Loop list'.

The Loop connector allows you to iterate through a list of results. In this example, we will use it to iterate through the data found within the previous Hunter connector step.

In order to specify the list you want to loop through, start by using the list mapping icon (found next to the list input field, within the properties panel) to generate the connector-snake.

While hovering over the 'List leads' step (with the tail end of the connector-snake), select leads from the list of output properties displayed. This will auto-populate a jsonpath within your list input field, and update the type selector to jsonpath.

For more clarification on the pathways you have available, open the Debug panel to view your step's Input and Output.

JSONPATHS: For more information on what jsonpaths are and how to use jsonpaths with, please see our pages on Basic data concepts and Mapping data between steps

CONNECTOR-SNAKE: The simplest and easiest way to generate your jsonpaths is to use our feature called the Connector-snake. Please see the main page for more details.

3 - Get lead details

The last step is to drag a Hunter connector inside the Loop Collection step itself. Set the operation to 'Raw HTTP Request'. As you can see from the Hunter API docs, the 'id' field is required in the resource path.

Use the connector snake and hover over the 'Loop Collection' step (with the tail end of the connector-snake) and select the jsonpath for the specified identifier from the list of output properties displayed.

In this case the jsonpath for 'Endpoint' is selected and it should appear similar to $ Then update the type selector to string, surround it with curly braces and prepend it with '/leads/'. It should look like: /leads/{$}.

INTERPOLATION: When you wish to include JSON generated data within another input/output result, use our Interpolation method as described here.

You can always inspect the logs of your workflow by using the ‘Debug’ tab available on the top of the Tray builder.

If you go through each execution of the 'Get Lead Details' step, you will see the results of each loop.

BEST PRACTICES: Whenever you do decide to create your own workflow, be sure to check out some of our key articles such as: