Integration
Connect Leadport to Landbot
When New Customer fires in Leadport, your agent runs Get customer in Landbot. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Leadport and Landbot to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)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)Example flows
What Leadport can start in Landbot
When New Customer in Leadport
then Get customer in Landbot
When New Customer in Leadport
then Update customer field in Landbot
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 Leadport and Landbot
Triggers and actions 1 trigger · 31 actions
Trigger
New CustomerTriggers when a new customer is added to your Leadport account.
Action
Add taskCreates a task for a Leadport customer, optionally assigned to a user with a planned date and priority.
Action
Add ticketCreates a new ticket for a customer in Leadport.
Action
Add ticket offerCreates an offer on an existing customer ticket in Leadport, with a name, amount and description.
Action
Add ticket saleRecords a new sale against a customer's ticket in Leadport, with its amount and optional custom template values.
Action
Create GMC (Golden Moment Call) LeadCreates a Golden Moment Call lead in Leadport, which triggers an immediate call between your team and the customer.
Action
Create or Update CustomerCreates a Leadport customer, or updates an existing one when a customer ID is given.
Action
Get CustomerReturns one Leadport customer by its ID.
Action
Get taskReturns a Leadport task with its details, including the customer, assignee, type, planned date and call count.
Action
Get ticketReturns a ticket's details, including its customer, assignee, status and form field values, plus the ticket form template.
Action
List ChannelsReturns the lead channels configured in your Leadport account.
Action
List Customer EventsReturns the activity events (calls, tasks, notes) recorded for a Leadport customer.
Action
List reasonsReturns the reasons configured in your Leadport account, optionally filtered by reason type.
Action
List tasks by customerReturns the tasks belonging to a Leadport customer.
Action
List tickets by customerReturns all tickets belonging to a Leadport customer.
Action
List usersReturns all active users in your Leadport account, with their names, emails and roles.
Action
Search CustomersFinds Leadport customers whose details match a keyword (name, email, phone).
Action
Archive customerArchives a Landbot customer so their conversation moves out of the active inbox.
Action
Assign customer to agentAssigns a Landbot customer conversation to a specific agent.
Action
Assign customer to botAssigns a Landbot customer to a bot, optionally starting the bot right away or from a specific node.
Action
Delete customerDeletes a Landbot customer.
Action
Find customers by name, email or phoneFinds customers whose name, email or phone starts with the text you give. Returns up to 100 matching customers.
Action
Get channelReturns a Landbot channel's details, including its name, type, active status and appearance settings.
Action
Get customerReturns a Landbot customer's profile, including name, channel, assigned agent, archive status and custom field values.
Action
Get customer fieldReturns the name, type and current value of one custom field stored on a Landbot customer.
Action
List channelsReturns the channels in your Landbot workspace, optionally filtered by type and active status.
Action
List customer messagesReturns the full conversation transcript for a Landbot customer — every message exchanged with them.
Action
List customersReturns the customers in your Landbot workspace, optionally filtered by channel, assigned agent, archive or WhatsApp opt-in status, or a name/email/phone prefix.
Action
List WhatsApp templatesReturns the WhatsApp message templates available to send to customers, optionally limited to one channel.
Action
Send text messageSends a text message to a Landbot customer on their channel.
Action
Send WhatsApp templateSends an approved WhatsApp template message to a Landbot customer, filling in its placeholders. Use it to reach a customer outside WhatsApp's 24-hour messaging window.
Action
Update customer fieldChanges the value of an existing custom field on a Landbot customer. The field must already exist on the customer.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Leadport
Leadport to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Leadport to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Leadport to MailchimpMailchimp marketing automation and email platform.
Leadport to StripeStripe is a payment processing platform for online businesses.
Leadport to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Leadport to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Landbot
HubSpot to LandbotHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LandbotSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LandbotSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LandbotGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LandbotGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LandbotGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Leadport and Landbot, answered
What can start an automation from Leadport?
Any of Leadport's 1 trigger in the catalog, including New Customer. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Landbot when something happens in Leadport?
Any of Landbot's 15 actions, including Send text message, Send WhatsApp template, Update customer field and Assign customer to agent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Landbot to Leadport?
Landbot has no triggers in the catalog today, so automations start in Leadport. If you need the other direction, ask: your agent reads Landbot's API documentation and adds it.
Do I have to build a connector for Leadport or Landbot?
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.
Can my AI client use Leadport and Landbot without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.