Integration
Connect DevCycle and Leadport
When New Feature Created fires in DevCycle, your agent runs Add task in Leadport, or New Customer in Leadport to Add project in DevCycle. 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 DevCycle and Leadport 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 DevCycle and Leadport can do together
From DevCycle to Leadport
When New Feature Created in DevCycle
then Add task in Leadport
When New Feature Created in DevCycle
then Add ticket in Leadport
From Leadport to DevCycle
When New Customer in Leadport
then Add project in DevCycle
When New Customer in Leadport
then Add feature in DevCycle
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 DevCycle and Leadport
Triggers and actions 2 triggers · 28 actions
Trigger
New Feature CreatedTriggers when a new feature is created in a DevCycle project.
Action
Add featureCreates a new feature flag in a DevCycle project, with optional variations, variables and per-environment targeting.
Action
Add projectCreates a new project in your DevCycle organization.
Action
Add variableCreates a new variable in a DevCycle project, optionally attached to a feature.
Action
Delete featureDeletes a DevCycle feature from a project, optionally deleting its associated variables too.
Action
Get featureReturns a DevCycle feature, including its variations, variables and environment targeting configurations.
Action
List environmentsReturns the environments (development, staging, production, etc.) in a DevCycle project, including their keys and SDK keys.
Action
List featuresReturns the features in a DevCycle project, optionally filtered by type, status, staleness, keys or a search term.
Action
List projectsReturns the DevCycle projects the connected account has permission to view.
Action
List variablesReturns the variables in a DevCycle project, optionally filtered by feature, type, status or search text.
Action
Update EdgeDBTurns EdgeDB on or off for a DevCycle project and returns the updated project.
Action
Update featureUpdates an existing feature in a DevCycle project, such as its name, description, type, tags, variations, variables or environment targeting.
Action
Update variableUpdates an existing variable in a DevCycle project, such as its name, description, type, tags or key.
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).
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 DevCycle
DevCycle to KobotoolboxMobile/offline survey and form data collection platform with an API to submit, export, and manage field...
DevCycle to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DevCycle to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DevCycle to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DevCycle to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
DevCycle to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Leadport
HubSpot to LeadportHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LeadportGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LeadportGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LeadportGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to LeadportGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to LeadportActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
DevCycle and Leadport, answered
What can start an automation from DevCycle?
Any of DevCycle's 1 trigger in the catalog, including New Feature Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Leadport when something happens in DevCycle?
Any of Leadport's 16 actions, including Create GMC (Golden Moment Call) Lead, Create or Update Customer, Add task and Add ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Leadport to DevCycle?
Yes. When something happens in Leadport, your agent can act in DevCycle too. This page covers both directions: Leadport's triggers and DevCycle's actions are listed here as well.
Do I have to build a connector for DevCycle or Leadport?
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 DevCycle and Leadport 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.