- A CRM or recruitment integration, such as Recruitee, Odoo or Zoho CRM.
- Zapier.
- The REST API or MCP server.
- A file upload under Update Leads.
How updates find the lead
An update is matched to a lead with these identifiers, in this order:- Octanist lead ID
- External lead ID
- Phone
Status flow
Status changes only move forward:
Every external update is logged in the lead history with its source, such as Recruitee, ClickUp, Zoho or API. Failed updates are logged too.
Settings
Won Lead Auto-Qualification
When a lead is marked as won, also mark it as qualified if it wasn’t already. The qualified conversion is then sent to your integrations before the won conversion. On by default. Keep this on when your CRM jumps straight from a new lead to a won deal. Your ad platforms then still learn from the qualified step.Won Lead Value Updates
Allow integrations to change the value of leads that are already won. Off by default. When off, value updates on won leads are logged but not applied. Turn this on when the final deal value is only known after the deal is won, for example after an invoice.Multiple Match Behavior
An email address or phone number can belong to several leads. Under When multiple leads match, choose what happens:With Update all, each lead gets the full value and its own conversion.
Same-Company Lead Matching
When an update finds no exact match, apply it to an open lead from the same company email domain. For example, a deal forjan@company.com can count toward a lead from sanne@company.com. Off by default.
- Exact matches always come first.
- Only open leads on exactly the same domain can match. Won and lost leads are never changed this way.
- Personal email providers, such as Gmail, Hotmail, Outlook, iCloud and Proton, internet providers such as Ziggo and KPN, and temporary email services are always excluded.
- When several open leads share the domain, Multiple Match Behavior decides what happens.