LeadMailbox connector icon

LeadMailbox Connector

Build in-app lead automations that post prospects into LeadMailbox campaigns, map custom fields and trigger SMS, email or telephony actions — all embedded inside your SaaS and scoped per customer account.

01

Faster lead capture

Push web and form leads into LeadMailbox instantly.

02

Field-level mapping

Map custom app fields to LeadMailbox campaign fields.

03

Reduce lead loss

Automate routing, SMS and call triggers to contact leads faster.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

Overview

Teams can post and route web and form leads into LeadMailbox campaigns, create company records and automate lead-driven SMS, email or telephony workflows. Cyclr maps your app fields into the LeadMailbox JSON/XML/Form payload and posts to campaign-specific endpoints as described in the vendor integration guide. (static.leadmailbox.com)

PRODUCT USE CASES

Top Use Cases for LeadMailbox Integrations

Enable customer-facing automations so each tenant can route leads into their LeadMailbox campaigns, trigger communications and keep audit trails — all with no separate integration projects.

Instant web-to-LeadMailbox posting

When a visitor submits a form, post a single-lead payload to the tenant’s LeadMailbox campaign endpoint to create a Lead record.

Automate routing and first-touch communications

After posting a lead, trigger Cyclr steps to send SMS or email follow-ups and call actions using LeadMailbox campaign fields.

Provision customer campaigns

Map new customer account fields to LeadMailbox Company fields and wire their campaign Post URL for tenant-scoped lead intake.

ORCHESTRATION

How LeadMailbox works with Cyclr

Cyclr sits between your SaaS product and LeadMailbox to handle authentication, govern access and orchestrate every API call per customer, at scale.

  1. 1

    Your SaaS product

    Your app requests an action for a specific customer.

  2. 2

    Cyclr orchestration

    Cyclr authenticates, applies policies and routes the request.

  3. 3

    LeadMailbox

    LeadMailbox processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore LeadMailbox methods you can orchestrate through Cyclr.

Leads1

Create Lead

Action

Create a lead in LeadMailbox.

TECHNICAL DETAILS

LeadMailbox integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing LeadMailbox integrations in Cyclr.

API and authentication

API host
https://api.leadmailbox.com
Authentication
Account name
Credentials

Account Name; Campaign Name or campaign Post URL (from LeadMailbox Settings).

Method categories

Post Leads; Company fields; web form posting; single-lead POST field mapping.

View vendor API documentation →

Pagination and rate limits

Pagination

No pagination — each request delivers a single lead to a campaign endpoint.

Rate limits

No public rate limits documented; confirm limits with LeadMailbox support or in Cyclr Console.

IMPLEMENTATION

Authentication at a glance

Cyclr installs require the LeadMailbox account name and targets campaign-specific POST URLs; confirm exact Console option during installation. (community.cyclr.com)

Authentication method
Account name
Credential required

Account Name; Campaign Name or campaign Post URL (from LeadMailbox Settings).

Before you begin:

Campaign Post URL must be obtained from LeadMailbox Settings for each account.

View setup guide

COMMON QUESTIONS

Frequently asked questions

It posts single-lead records into LeadMailbox campaigns and creates Company/lead records, enabling automated SMS, email and telephony workflows driven by campaign fields. The connector uses the vendor Post Leads method to deliver leads. (static.leadmailbox.com)

Authentication uses the LeadMailbox account name and the campaign-specific POST URL; Cyclr requires the account name at install so posts target the correct campaign. Confirm the exact install fields in Console. (community.cyclr.com)

Yes. Install and configure each customer’s account name or campaign Post URL so workflows post leads into that customer’s LeadMailbox campaign, preserving tenant isolation.

Yes. Cyclr workflows can expose the Post Leads action as an MCP tool with preconfigured mappings and governance, letting product teams control which customers can post leads.