Folk
Create a Person in your Folk CRM for every lead captured on your demos.
The Folk integration turns each captured lead into a Person record in your Folk workspace. Folk automatically checks for duplicates when a person is created, so a returning lead updates the existing record instead of piling up copies.
You can connect one Folk workspace per account, and optionally drop every new lead straight into one of your Folk groups (like your "Leads" list).
Create an API key
Escourtly authenticates with a Folk API key.
Open Folk's API settings
In Folk, go to Settings → API.
Connect Folk
Paste your key
Paste the API key. It's stored encrypted and never shown again.
Pick a group (optional)
Click Load my Folk groups and choose the group new leads should land in — so they show up in one of your Folk lists. Leave it on No group to add people without one.
Don't type the group id from the URL
The id in a Folk group's web-app URL is a bare UUID, not the API's grp_… id — pasting it fails. The picker fetches your real groups for you, so you never have to copy an id by hand.
Send a test lead
Click Manage → Send a test lead and check your workspace — a sample Person should appear.
What gets synced
| Lead field | In Folk |
|---|---|
| The Person's primary email address. | |
| Name | Split into first / last name, with the full name kept too. |
| Phone | Added as the Person's phone when present. |
| Company | Linked as the Person's company by name — no email-domain guessing, so a company syncs even for personal-email leads. |
| Group | Every new Person is added to the group id you configured (if any). |
Folk de-duplicates for you
Folk checks for duplicates when creating a person, so re-submissions merge into the existing record rather than creating a second copy — you don't need a matching key like some CRMs.
A bad phone never costs you the lead
If Folk rejects a phone number, we retry the person without it — so the Person still lands, just without that phone. Encourage viewers to include a country code (e.g. +1…) for the cleanest result.
Delivery and failures
- A successful create is recorded as the connection's last status.
- Rate limits and
5xxretry automatically; an invalid key or a rejected value is recorded so you can fix it.