// automation and data tools
Via APITray.ai email verification with pingutil
Tray workflows stitch together forms, CRMs and marketing automation, and they forward every address they receive without asking whether it works. An HTTP Client step that calls pingutil adds a verification status and spam verdict that a Boolean or Branch step can act on before anything is written.
Where it connects: HTTP Client connector (POST request step)
What goes wrong without it
- Our lead-routing workflow assigns reps to contacts whose email bounces on the first touch.
- Fake signups from a free-trial form are polluting the marketing automation database.
- We have no single place where every inbound address gets checked before it fans out to five systems.
What you can do with Tray.ai and pingutil
Verification step in a central lead router
Put one HTTP Client call at the top of the routing workflow so every source gets the same status and reason before assignment.
Spam screening for trial signups
Call /v1/lookup with skip_enrichment: true and stop the workflow on verdict.is_spam so disposable trial accounts never reach the MAP.
Company data for routing
For company emails, a full lookup returns company.employee_size_estimate and company.industry to drive territory or segment rules.
Set it up
- 1
Store your pingutil key as a Tray authentication or config value rather than typing it into the step.
- 2
Add an HTTP Client step with method POST and URL https://pingutil.com/v1/verify.
- 3
Add headers Authorization: Bearer pk_live_... (from the stored value) and Content-Type: application/json.
- 4
Set the body type to raw JSON with the body below, using a JSONPath reference to the trigger's email.
- 5
Add a Branch step on the response body status with valid, risky, invalid and a default branch.
- 6
Configure the step's error handling so a non-2xx response continues on the default branch as unverified.
{
"email": "{$.steps.trigger.body.email}"
}What to do with each result
| pingutil result | Action in Tray.ai |
|---|---|
| status = "valid" | Continue to assignment and CRM create |
| status = "risky" | Create the record with a risk field, hold from automated outreach |
| status = "invalid" | Stop the branch and log the reason |
| Default branch (unknown or error) | Create as unverified and queue a re-check |
Limits to plan for
- Tray's HTTP Client fails a step on non-2xx responses unless you configure the expected status codes or error handling.
- pingutil allows 60 requests a minute and 300 verified addresses a day (3,000 a month) per account. Those are Free plan limits; Enterprise has custom limits.
- Verification can take up to about 25 seconds on slow mail servers; use /v1/lookup with skip_enrichment for latency-sensitive paths.
Tray.ai documentation
- tray.ai/documentation/connectors/core/http-client
- tray.ai/documentation/connectors/core/http-client/http-client-operations-sample-payloads
Tray.ai is a trademark of its owner. This integration uses Tray.ai's documented extension points; it is not an official Tray.ai app.
Common questions
- How do I reference the trigger email in the body?
- Use Tray's JSONPath reference to the trigger output, adjusting the path to the field name your trigger actually provides.
- Can I verify many addresses per step?
- Yes, POST up to 50 addresses as { "emails": [...] } to /v1/verify/batch and loop over the results list.
Stop bad addresses in Tray.ai today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Tray.ai setup will receive.