# Connect Docparser to LeadExec

When **Parsed Document Data Available** fires in [Docparser](https://apiant.ai/connections/docparser), your agent runs **Add order** in [LeadExec](https://apiant.ai/connections/leadexec). Describe the whole flow and it is built, tested on every scenario and kept running.

Docparser **2** triggers Docparser **2** actions LeadExec **7** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Docparser and LeadExec to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Docparser can start in LeadExec

- When **Parsed Document Data Available** in Docparser then **Add order** in LeadExec
- When **Parsed Table Row Available** in Docparser then **List lead types** in LeadExec

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Docparser and LeadExec

## Triggers and actions 2 triggers · 9 actions

- Trigger

**Parsed Document Data Available**

Triggers whenever a new Document is processed and parsed data is available.

- Trigger

**Parsed Table Row Available**

Triggers whenever a new Document is processed and parsed table rows are available.

- Action

**Fetch Document From URL**

Fetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).

- Action

**Upload Document**

Uploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).

- Action

**Add client**

Creates a new client record in LeadExec, including its client field values.

- Action

**Add delivery account**

Creates a new delivery account for a LeadExec client, setting its delivery method, price, lead caps, status and offer details.

- Action

**Add order**

Creates a new lead order for a client, with its start and end dates, renewal option and ordered items.

- Action

**List delivery accounts**

Returns all delivery accounts for a LeadExec client, including pricing, lead caps, status, criteria and delivery method details.

- Action

**List lead types**

Returns every lead type set up in your LeadExec account.

- Action

**List orders**

Returns client orders in LeadExec, optionally narrowed to one order, a client, an order status, or orders starting on or after a date.

- Action

**Update client**

Updates an existing LeadExec client record, including its status, assignments, portal login and client field values.

## Each app on its own

- [ **Docparser** Docparser converts your PDF documents into structured and easy-to-handle data.](https://apiant.ai/connections/docparser)
- [ **LeadExec** LeadExec provides centralized lead distribution.](https://apiant.ai/connections/leadexec)

Reviews

## What our customers say

## More from Docparser

- [ **Docparser to Prismix** Real-time uptime for 77 AI APIs (OpenAI, Anthropic, Cursor, Gemini) — free JSON endpoint, no auth required](https://apiant.ai/connect/docparser-to-prismix)
- [ **Docparser to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/docparser-to-hubspot)
- [ **Docparser to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/docparser-to-salesforce)
- [ **Docparser to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/docparser-to-slack)
- [ **Docparser to Google Sheets** Google Sheets](https://apiant.ai/connect/docparser-to-google-sheets)
- [ **Docparser to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/docparser-to-gmail)

## More into LeadExec

- [ **HubSpot to LeadExec** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-leadexec)
- [ **Salesforce to LeadExec** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-leadexec)
- [ **Slack to LeadExec** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-leadexec)
- [ **Google Sheets to LeadExec** Google Sheets](https://apiant.ai/connect/google-sheets-to-leadexec)
- [ **Gmail to LeadExec** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-leadexec)
- [ **Google Calendar to LeadExec** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-leadexec)

Questions

## Docparser and LeadExec, answered

###

### What can start an automation from Docparser?

Any of Docparser's 2 triggers in the catalog, including Parsed Document Data Available and Parsed Table Row Available. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in LeadExec when something happens in Docparser?

Any of LeadExec's 7 actions, including Update client, Add client, Add delivery account and Add order. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from LeadExec to Docparser?

LeadExec has no triggers in the catalog today, so automations start in Docparser. If you need the other direction, ask: your agent reads LeadExec's API documentation and adds it.

###

### Do I have to build a connector for Docparser or LeadExec?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
