Use Zapier, Make, n8n or Pipedream with TruLata
Send each new lead to your other apps, bring leads and outcomes back in, and catch new blog posts, through webhook and HTTP steps.
#What you can automate
Four things, in both directions. Each new lead goes out to the tools your team already runs. Leads from anywhere else come in and land on your Leads tab. A lead's outcome is written back from wherever your team records it. And each blog post goes out once it is published.
For example: a new lead posts to your team's Slack channel and adds a row to a Google Sheet. A deal marked won in your CRM marks the same lead won in TruLata. A landing page form TruLata does not read sends its leads in.
#How each tool connects today
Zapier: through Webhooks by Zapier and its HTTP steps. TruLata's own Zapier app is in review and not public yet.
Make: webhook and HTTP modules. n8n: Webhook and HTTP Request nodes. Pipedream: HTTP trigger and request step.
Integrately has its own TruLata app: see Use Integrately with TruLata.
All of them use the same key. Make one first: Make, copy or revoke an API key.
#Receive new leads
- In your tool, add a webhook trigger and copy the address it gives you.
- Subscribe that address to
lead.createdwith one call to/v1/hooks, with your key in the header. - From then on, each new lead arrives at that address within about two minutes.
#Send leads in, or mark them won or lost
Add an HTTP request step that calls /v1/leads to add a lead, or /v1/leads/{id}/status to set an outcome, with your key in the header. See Send leads in and set outcomes through the API.
#Questions
Is TruLata on Zapier?
TruLata works with Zapier today through Webhooks by Zapier and its HTTP steps. TruLata's own Zapier app is in review and is not public yet.
Can I use my own code?
Yes. Anything that can send an HTTPS request with a header can use the API.
Related articles
Ask on the Ask TruLata tab of your dashboard and it answers from your own numbers, or opens a ticket for a person. Or email support@trulata.com and a person on our team replies.

