Kuration Alex: Send Leads into the CRM

Overview#

Alex is Kuration's AI research agent. It can run on a schedule, for example "every Monday, find 20 new heads of sales at software companies in Texas". Add an HTTP API column to the Kuration project and each lead Alex finds goes straight into AutomateNexus CRM. The CRM recognizes people it already has, so the same person sent twice stays one person.

You can also find leads without leaving the CRM: open Lead research, or ask Karrie ("find 25 heads of sales at software companies in Texas"). This guide is for when you want Alex's schedule to do it for you.

Prerequisites#

• A Kuration project that Alex fills, with an email or a phone column. The CRM needs one of the two for each lead.
• An API key from the CRM, made under Administration → Integrations → Developer → API keys, with read and write access. The key belongs to your organization, so keep it private.

The Address and the Key#

Send each lead as a POST request to:

https://app.automatenexuscrm.com/functions/v1/webhooks/custom

with these headers:

x-api-key: YOUR_API_KEY
Content-Type: application/json

What to Send#

{
  "event_type": "lead.created",
  "data": {
    "first_name": "Jane",
    "last_name": "Smith",
    "email": "jane@example.com",
    "phone": "+12125550123",
    "company_name": "Acme Corp",
    "job_title": "Head of Sales",
    "linkedin_url": "https://www.linkedin.com/in/janesmith",
    "lead_source": "kuration",
    "form_name": "Alex: Texas sales leaders",
    "lead_id": "ROW_ID"
  }
}

• Who the person is: first_name and last_name, or full_name; email; phone; company_name; job_title. Each lead needs at least an email or a phone.
• Anything else you send (here, linkedin_url) is kept with the lead as one of its answers, so nothing Alex found is lost.
• lead_source is how the lead shows in reports. Use kuration for every lead from Alex.
• form_name names the list. Use your automation's name, so you can see where each lead came from.
• lead_id is your Kuration row's own id. When the same row is sent again (Alex re-runs, for example), nothing new is added.
• Which workspace: the lead goes to your default workspace. To choose another, add "workspace": "Sales" (its name) or "workspace_id".

When the email or phone belongs to someone already in the CRM, the lead joins that person: their empty fields are filled in, and nothing anyone typed is replaced. Otherwise a new person is added as a lead. Either way your New lead workflows run, so a welcome email or a task for the owner starts on its own.

Setting It Up in Kuration#

1. Open the project Alex fills and add an HTTP API column.
2. Set the method to POST, the address above, and the two headers.
3. For the body, use the JSON above and put each of the project's columns in its place (email, name, company and so on).
4. Set the column's rate limit to 60 a minute or fewer. The CRM takes up to 120 requests a minute for each key.
5. Let the column run for new rows, then give Alex its schedule.

Checking It Worked#

Send one row first. The column's answer should say "success": true. Under results it says "new_contact": true for a new person, or false for someone the CRM already had. The person appears under People with the source kuration.

Troubleshooting#

Costs#

What Alex and the HTTP API column use is billed by Kuration to you.