Messages and sources

Leadveyor works with messages: anything a potential customer sends a business — an email, a website form, a chat message, a call transcript, a request from a lead platform. Messages arrive through sources, and whatever the channel, each one is turned into the same shape before anything else happens.

Email
In / out
forwarded from your mailbox, or sent to your address by a lead platform
Website form
In / out
your HTML form posts straight to your form link
Form builders
In / out
Unbounce, Framer, Webflow, Typeform… via their webhook
Your apps
In / out
CRM, chat, call transcripts, anything — POST /v1/inbounds
Source
Code

One per entry point. Gives you an email address, a form link, or is used with an API key.

Knows the workspace, the profile to score with, and whether it is active.

Message
Code
  • text
  • subject
  • from (name, email, phone)
  • form fields, as sent
  • channel
  • received at
Many channels, one shape: every source turns what it receives into the same message.

Channels on the left reach a source in the middle, which produces one normalized message on the right: text, subject, sender (name, email, phone), form fields exactly as sent, the channel and the time it was received.

Channels

ChannelHow it reaches LeadveyorTypical use
EmailA unique address of yours, e.g. acme-x7k2q@in.leadveyor.com. You forward your enquiries mailbox to it, or give it to a lead platform as the recipient.Contact mailboxes, notifications from lead platforms, enquiries forwarded by staff
Web formA unique link your form posts to — a plain HTML form, or a webhook in a form builder (Unbounce, Framer, Webflow, Typeform…). No API key needed.Website enquiry forms, landing pages
APIYour program sends POST /v1/inbounds with an API key: free text, an email, form fields, or all of them.CRMs, chat tools, call transcription, custom apps

More channels (Telegram, ad lead forms, CRM connectors) come as further source types; whatever the channel, the rest of the path is the same.

What a source is

A source is one entry point for messages. It holds:

  • The way in — the email address, the form link, or (for the API) a name your program refers to.
  • The workspace the messages belong to.
  • The profile to score its messages with — or the workspace default. Different sources can score with different profiles: one form for corporate events, another for weddings.
  • Its status — active, or paused (a paused source refuses new messages).

Create one source per entry point you want to tell apart in reports and settings. All messages keep a reference to their source, so you can always see where a lead came from.

One shape for every message

Before reading a message, Leadveyor normalizes it:

  • Email — sender name and address, subject, and the text body (from HTML when there is no text part); quoted history and signatures stay, since forwarded enquiries live there.
  • Forms — every field as sent, with the names your form uses ("full_name", "Your message", "event_date"). Nothing has to be mapped: the model reads the field names like a person would. Technical fields (page URL, user agent, tracking IDs) are ignored when reading.
  • API — any combination of free text, an email object and form fields, plus your own metadata and an externalId.

Normalizing means one set of rules and one profile can handle every channel: a wedding enquiry scores the same whether it came by email or by form.

Special cases handled at the door

  • The same message twice — a forwarded email that arrives twice, a form submitted again by a retrying builder, an API call repeated after a timeout: each message carries an identity (the email's Message-ID, the form's idempotency key, your externalId), and a repeat is recognised and processed once.
  • Forwarding confirmations — Gmail and Outlook first send a "confirm forwarding" email to a new address. Leadveyor recognises it, doesn't treat it as a lead, and shows the confirmation link or code on the source.
  • Bots on forms — a hidden _hp field catches simple bots: submissions with it filled are dropped silently. Each form also accepts at most 120 submissions a minute.
  • Signed email delivery — incoming email is accepted only with a valid signature from the mail provider, so nobody can inject fake "emails" by calling the endpoint directly.

Workspaces

A workspace is one business: its sources, profiles, leads, contacts and settings live together and are never mixed with another workspace's. An account can have several workspaces — an agency running clients, a group with several brands — and people and API keys can be given access to one workspace or to all of them.

Test and live

Every message is either live or test. Messages sent with a test API key are test messages: they are processed exactly like live ones, but their leads, contacts and webhook deliveries are kept apart from live data. Build and check an integration with a test key, then switch to a live key. Messages from email and form sources are always live.

Was this page helpful?