Skip to main content
Lead sources are the durable connections that bring new leads into RevDesk. Jobs define what a coworker should do when a source delivers a lead. Keeping those decisions separate lets one source feed several jobs, and lets each job own its team, coworker, outcome, and guardrails.

​
Create a lead source

Open Directory → Lead sources. Workspace admins can create and administer sources; members can select sources they are allowed to use without seeing credentials.
1

Choose the source type

Select ADF email/webhook, generic webhook, CRM/provider, or a RevDesk hosted form.
2

Name and locate it

Give the source a recognizable name and, when applicable, assign its dealership location. Leave location empty for a workspace-wide source.
3

Map the payload

Match incoming fields to phone, name, email, country, external ID, and source. Nested JSON fields use dot paths such as contact.phone.
4

Connect and verify

Copy the generated address and secret into the provider, then send a live test. The card shows the latest delivery, test result, and any mapping or authentication error.
Each source card shows its provider and format, location, enabled state, intake address, recent delivery health, test status, and connected jobs. Disabling or archiving a source stops new deliveries without changing its history.

​
Generic webhook

Send JSON or URL-encoded form data to the source-specific endpoint:
The intake token in the URL identifies the source and is a credential. Keep the URL private. A connection can also authenticate with the source secret as a Bearer token:
For providers that sign requests, send the lowercase hex HMAC-SHA256 of the raw request body in X-RevDesk-Signature (an optional sha256= prefix is accepted). The HMAC key is the source secret.

​
Payload mapping

Without a custom map, RevDesk recognizes common names including phone, phone_number, mobile, name, first_name, last_name, email, external_id, lead_id, country, and source. A saved map takes priority and may point to nested values:
Phone is the key field for call and message work. Always send E.164 when possible, such as +14155551234. The original payload is retained with the intake attempt for troubleshooting and job context.

​
Responses and health

  • 200 means the delivery was accepted and reports the ingestion outcome.
  • 400 means the body or mapping was invalid.
  • 401 means the supplied secret or signature was invalid.
  • 403 means the source is disabled.
  • 404 means the intake token does not resolve, commonly after rotation.
  • 429 means the source rate limit was exceeded; retry after the Retry-After interval.
Every attempt updates the source card. Use Send test after setup or mapping changes, and confirm both a successful delivery and the expected normalized lead before enabling production traffic.

​
Rotate credentials

Admins can rotate a source from its card. Rotation issues a new intake URL token and secret immediately; the old values stop resolving. Update the sender, run a live test, and only then resume traffic. Rotation does not change the source ID, delivery history, field mapping, or connected jobs.

​
Connect a source to jobs

A source may feed multiple jobs. Connect it from the source card or select it while creating a job. Each matching delivery opens work independently for every connected job. Team ownership belongs to the job, not the source. Admins and full-scope users may leave a job workspace-wide or choose an allowed team. Team-scoped members must choose one of their teams.

​
Hosted and embedded forms

RevDesk hosted forms keep their published URLs:
Existing embed snippets continue to work. Form IDs, branding, domain allowlists, and submission history are preserved when the form is connected to a lead source. Cross-origin embeds remain subject to their configured domain allowlist, honeypot, CORS, and durable rate limit; the same-host hosted page also uses browser bot protection.

​
ADF sources

ADF sources can receive either ADF XML by webhook or ADF email at the address shown on the source card. Both transports resolve the same lead source, apply the saved mapping, log the attempt, and feed the same connected jobs.

Speed to Lead

Turn a new source delivery into immediate follow-up.

Webhook events

Subscribe your systems to call, message, and job outcomes.