Work with leads

Every form submission and chatbot lead step creates a lead. Your team works with leads in Studio under Forms & leads → Leads.

CRM push, the Leads API and retention cover Development leads only

Today these three features only see leads from your Development website. Leads from the live website can be viewed, assigned, merged and exported in Studio, and they reach your webhooks as lead.created events, but they are not pushed to a CRM, not readable through the Leads API and not cleaned up by retention yet.

Follow up a lead

• Choose Which website: Development or Live website (shown once Production is active).
• Filter by status, source and text, and choose whether to include test leads (Hide tests, Show tests, Only tests).
• Open a lead to set its Status and Assigned to, and to Add note.

Sales and support people see the leads assigned to them; admins see all leads.

Merge duplicates

When a lead shares an email address (ignoring case) or a phone number (at least 7 digits) with other leads, it shows This looks like a lead you already have.

1. Click Review and merge.
2. Under Merge into this lead, tick the leads to fold in.
3. Click Merge lead (or Merge N leads).

Empty contact fields on the kept lead are filled from the merged ones. Merged leads show Merged into another lead, and a lead.merged webhook event is sent.

Export to a spreadsheet

Set your filters, then click Export CSV. The file opens safely in Excel and Google Sheets: every cell is quoted, and cells that could be read as formulas are neutralised. One export holds up to 50,000 leads. Exports are recorded in the audit log.

Only organization admins and site admins can export.

Remove old personal data (retention)

Under Forms & leads → Settings, the card Lead retention lets a site admin:

1. Turn on Anonymise old leads.
2. Set Keep leads for (days), between 30 and 3,650 days (365 by default).
3. Click Save retention.

Every hour, Atlas strips the name, email, phone, company, message, form answers and chatbot message text from leads older than that. The status and history stay, and the lead shows Personal data removed. Retention is off until you save a policy.

Send leads to your CRM

Atlas can post every new lead to any HTTPS endpoint that accepts JSON: your CRM’s inbound API, an automation tool or your own service. There are no built-in HubSpot, Salesforce or Pipedrive connectors; use their HTTP intake endpoints with an API key header.

1. Go to Integrations → CRM and click Connect a CRM.
2. Enter a Name and the HTTPS Address.
3. Under Authentication, choose Send a header and enter the Header name (for example Authorization) and Header value. The value is stored encrypted and never shown again.
4. Under Fields to send, map each CRM field to a lead field or Fixed text, or click Start from common fields.
5. Click Connect, then Send test lead from the row menu to check it.

How delivery works:

• Each new lead is sent once per connection as a POST with X-Atlas-Event: lead.created and an X-Atlas-Delivery id that stays the same on retries. Test sends use X-Atlas-Event: lead.test.
• Anything other than a 2xx answer is retried after 1, 2, 4, 8 and 16 minutes, then marked failed. The row menu’s Delivery log shows the last 50 attempts.
• CRM requests are not signed (unlike webhooks), so protect the endpoint with the header.
• Leads marked as tests in Studio are not sent.
• You can have up to 10 connections per site environment, and Pause, Resume or Remove each.

Let another system read leads (Leads API)

Under Integrations → Leads API, click New key, give it a Name, choose what The key may do (Read leads, Change lead status) and an expiry (30, 90, 180 days or 1 year). The key is shown once. Full details: Leads API reference.

What to read next

Leads API referenceWebhooksForms and leads