Inbound Agent Configuration Guide

This setup process configures how the Inbound Agent (Lead Qualifier) receives, understands, and processes incoming leads from external systems.

Revscale supports two inbound methods:

• Email (Form Submission Monitoring)
• Webhook (Direct Integration)

Both methods rely on one-time field mapping so incoming data can be used consistently moving forward.

Choosing an Inbound Method

Email (Form Submission Monitoring)

Choose Email if:

• Leads arrive as form submission emails
• Emails are sent from a consistent sender address
• You want Revscale to monitor your inbox and engage leads automatically

Best for: Website forms, marketing tools, platforms that only send lead notifications via email.

Webhook (Direct Integration)

Choose Webhook if:

• Your system can send HTTP requests
• You want real-time ingestion
• You have structured data available

Best for: CRMs, custom applications, engineering-led integrations.

How Inbound Processing Works (Both Methods)

Regardless of method, Revscale follows the same model:

1. Receive incoming data (email or webhook)
2. Apply a one-time field mapping configuration
3. Normalize the data into Revscale fields
4. Trigger lead engagement automatically for all future events

You only need to revisit configuration if your data format changes.

Method 1: Configuring Inbound via Email

Overview

Email inbound works by monitoring emails from a specific sender address (usually a form provider). When a matching email is received, Revscale parses the contents and maps the data to lead fields.

Step 1: Select Email as the Inbound Method

In the inbound agent settings:

• Select Inbound Method: Email

Step 2: Enter the Sender Email Address

Enter the email address that sends form submissions to your inbox.

Examples:

• no-reply@webflow.com
• forms@typeform.com
• leads@hubspot.com

Revscale will monitor only emails from this address.

If the sender address changes, the agent will stop triggering until updated.

Email Field Mapping (One-Time Setup)

Why Field Mapping Is Required

Form submission emails are unstructured. Each provider formats emails differently.

Field mapping tells Revscale:

• Which text represents the lead’s name
• Which value is the email address
• Which content is the message or inquiry
• How to interpret custom fields

This mapping is saved and reused for all future emails.

Email Mapping Options

Option 1: Map Using Email Preview

When a form submission email is received, Revscale shows a preview of the email content.

You can:

• Identify values in the email
• Assign them to Revscale fields (Name, Email, Phone, Message, etc.)

This is the recommended approach when email formatting is consistent.

Option 2: Manual Field Mapping

You can also manually define fields by entering:

• Field Name — the label as it appears in the email
• Field Description — what the value represents

Example:

Revscale uses this information to locate and map values automatically for future emails.

Step 3: Test and Save

• Submit a test form
• Confirm fields map correctly
• Save the configuration

The inbound agent will now process all future emails using the saved mapping.

Method 2: Configuring Inbound via Webhook

Overview

Webhook inbound allows external systems to send structured JSON data directly to Revscale in real time.

During setup, you define how Revscale should interpret the payload schema. This is a one-time configuration applied to all future requests.

Step 1: Select Webhook as the Inbound Method

In the inbound agent settings:

• Select Inbound Method: Webhook

Step 2: Webhook URL & Authentication

Webhook URL

• A unique webhook URL is provided
• All requests should be sent to this endpoint
• Only HTTP POST with JSON is supported

API Key

• Generate an API key during setup
• Include it in every request

Example:

Authorization: Bearer YOUR_API_KEY

Requests without a valid API key will be rejected.

Custom Headers (Optional)

You may define additional headers for metadata or routing.

Examples:

X-Source-System: WebsiteForm
X-Environment: Production

Webhook Field Mapping (One-Time Setup)

Why Field Mapping Is Required

Even structured payloads differ across systems.

Field mapping defines:

• Where each value exists in the payload
• How it should map to Revscale lead fields

This configuration is saved and reused for all future webhook requests.

Webhook Mapping Options

Option 1: JSON Extract Mapping (Recommended)

Use when payloads are nested or complex.

Example Payload:

{
  "lead": {
    "name": "Jane Doe",
    "email": "jane@example.com",
    "company": "Acme Inc"
  },
  "message": "Interested in pricing"
}

Example Mappings:

Option 2: Manual Key–Value Mapping

Use when payloads are flat and predictable.

Example Payload:

{
  "name": "Jane Doe",
  "email": "jane@example.com",
  "message": "Interested in pricing"
}

Example Mappings:

Step 3: Test and Save

• Send a test webhook request
• Confirm values are extracted correctly
• Save the configuration

All future webhook events will now follow the saved mapping.

Email vs Webhook Comparison

Updated on: 30/12/2025