WhatCounts is an email service provider helping you send what counts with an amazing platform and full-service agency to back it up.
WhatCounts is a service connector. WhatCounts provides data management, software, and services to marketing professionals.
When using the WhatCounts connector, the first thing you will need to do is go to your Tray.io account page, and select the workflow you wish to work on. Once in the workflow builder itself, search and drag the WhatCounts connector from the connectors panel (on the left hand side) onto your workflow.
With the new WhatCounts connector step highlighted, in the properties panel on the right, click on the
Authenticate panel followed by
Add new Authentication (located under the Authentication input field).
This will result in a Tray.io authentication pop-up window. The first page will ask you to name your authentication, and state which type of authentication you wish to create ('Personal' or 'Organisational').
As you can see, the next page asks you for your 'Account name' and 'Api password' credentials.
In order to get these fields, head to your WhatCounts dashboard. Click on the 'Profile' icon on the top right hand corner of the navigation bar. Navigate to 'Set up API' from the 'API management' option of the dropdown menu.
Here you can find your exsiting API password or generate a new API password.
To get the accout name head to 'My Profile'. Your account name is the value of 'Realm'.
Once you have added these fields to your Tray.io authentication popup window, click on 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.
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')Copy
As of version 1.0, you can effectively create your own operations.
This is a very powerful feature which you can put to use when there is an endpoint in WhatCounts which is not used by any of our operations.
To use this you will first of all need to research the endpoint in the WhatCounts API documentation v1.0 , to ** find the exact format** that WhatCounts 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 WhatCounts is:
For example, say that the 'List lists' operation did not exist in our WhatCounts connector, and you wanted to use this endpoint, you would use the WhatCounts API docs to find the relevant endpoint - which in this case is a
GET request called:
More details 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 List lists information with the following settings:
Query Parameter: Key:
Body Type :
Final Example outcome being: <Content type link TBD>
TRAY POTENTIAL: Tray.io 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 Tray.io and the WhatCounts 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 WhatCounts connector, to get a subsriber information with a given email address.
The steps will be as follows:
Setup using a manual trigger and list all subscribers in your account.
Add the Loop collection connector to iterate over each subscriber.
Gather the information available for each subscriber.
The final outcome should look like this:
1 - Setup Trigger & List subscribersCopy
Once you have clicked 'Create new workflow' from your main Tray.io dashboard named it, select the Manual trigger from the trigger options available:
After you have been redirected to the Tray.io workflow dashboard, from the connectors panel on the left, add a WhatCounts connector to your second step. Set the operation to 'List subscribers'.
Feel free to re-name your steps as you go along to make things clearer for yourself and other users.
Now when this workflow is run, it will pull down a list of subscribers from your WhatCounts account.
2 - Add a loop collectionCopy
Next, search for the 'Loop collection' connector within your connector panel, and drag it into your workflow as your next step. Set your operations to 'Loop list'.
The Loop Collection 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 WhatCounts 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 subscribers' step (with the tail end of the connector-snake), select
results 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.
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.
This will enable us to iterate over the list of subscribers, and perform operations for each one, during each loop cycle.
3 - Get a single subscriber information with an emailCopy
The last step is to drag a WhatCounts connector inside of the Loop Collection step itself. Set the operation to 'Get subscriber by email'. As you can see, the 'Email' field is required.
Once the workflow run, you will be able to gather the information available for each subscriber.