Where leads come from, Rules and Connections
The CRM's Set up pages for forms, automatic rules, API keys and webhooks. Check what each page says before relying on it.
Under the CRM menu, a Set up group can show five pages. They are for the people who run the CRM, and a person who is not an owner or admin is told "This page is for the people who run the CRM".
| Page | What it is meant to do | Today |
|---|---|---|
Where leads come from (#/leadsin) |
Make an address a website form or tool can post enquiries to. Each lead arrives in the Leads inbox and is marked if it looks like spam. | The CRM can make these addresses. The public receiver is not switched on yet, so a form on a website cannot reach it. |
Rules (#/rules) |
"When this happens, and these things are true, do these things." Start from a ready-made rule and change it. | Not connected. The page asks the CRM for your rules and cannot get an answer yet. See What a workflow is. |
Connections (#/connect) |
API keys, webhooks and the assistant connector. | Not connected for the same reason. |
Lead report (#/leadreport) |
Where enquiries came from, this month's use and a person's data export. | May show nothing until the CRM service is updated. |
Alerts (#/crmbell) |
New leads and answers due. | Reads what the CRM holds. |
What stays true once they work
- A rule never starts another rule, and a rule that does too much in an hour is paused for you to look at.
- A secret, such as an API key, is shown once, then never again.
- A form's enquirer is never told more than a fixed acknowledgement, and what they typed is read only in the app.