Integration
Connect Condens and Pelcro
When Participant Created fires in Condens, your agent runs Create Customer in Pelcro, or Customer Created in Pelcro to Add project in Condens. 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 Condens and Pelcro 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 Condens and Pelcro can do together
From Condens to Pelcro
When Participant Created in Condens
then Create Customer in Pelcro
When Artifact Published in Condens
then Update customer in Pelcro
From Pelcro to Condens
When Customer Created in Pelcro
then Add project in Condens
When Customer Updated in Pelcro
then Add project folder in Condens
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 Condens and Pelcro
Triggers and actions 7 triggers · 35 actions
Trigger
Artifact PublishedFires once for each published artifact in the chosen Condens project.
Trigger
Participant CreatedTriggers when a new Participant was created.
Action
Add projectCreate a project.
Action
Add project folderCreate a project folder.
Action
Create or Update ParticipantCreates or Updates a Participant
Action
Create or Update SessionCreates or Updates a Session
Action
Delete participantDelete a participant.
Action
Delete projectDelete a project.
Action
Delete project folderDelete a project folder.
Action
Delete sessionDelete a session.
Action
Find a ParticipantSearch for a Participant by name or fields attached to it
Action
Find a SessionSearch for a Session by title or fields attached to it
Action
Get participantGet a participant by id.
Action
Get projectGet a project by id.
Action
Get sessionGet a session by id.
Action
List artifactsList artifacts.
Action
List participantsList participants, paginated with filter/sort.
Action
List project foldersList project folders.
Action
List projectsList projects, paginated with filter/sort.
Action
List sessionsList sessions, paginated with filter/sort.
Action
List usersList users.
Action
List workspacesList workspaces.
Action
Update artifactUpdate an artifact.
Action
Update projectUpdate a project.
Action
Update project folderUpdate a project folder.
Trigger
Customer CreatedTriggers when a user registers via the Pelcro Platform. This means that a customer record exists in Pelcro and has a unique email address, password, and customer ID associated to it.
Trigger
Customer UpdatedTriggers when a customer is updated in Pelcro.
Trigger
Newsletter CreatedTriggers when a new newsletter subscription is created in Pelcro.
Trigger
Newsletter UpdatedTriggers when an existing Pelcro newsletter subscription is updated, such as a change to the subscriber's mailing lists or consent.
Trigger
Subscription CreatedTriggers when a new subscription is created in Pelcro.
Action
Add addressCreates a new shipping, billing or primary address for a Pelcro customer.
Action
Add couponCreates a new discount coupon on your Pelcro site, with either a fixed amount or a percentage off.
Action
Create CustomerCreates a new customer on your Pelcro site.
Action
Create NewsletterCreates a newsletter subscriber in Pelcro with their email, signup source and optional consent details.
Action
Create PlanCreates a new pricing plan under a Pelcro product, setting its price, currency, billing interval and subscription behavior.
Action
Create ProductCreates a product in your Pelcro site. Plans and their prices are added under a product.
Action
Create SubscriptionCreates a subscription for a Pelcro customer on a plan, optionally with a coupon, trial period or gift details.
Action
Get couponReturns a single coupon by id, including its code, discount, duration, redemption count and expiration.
Action
Get newsletterReturns a single newsletter subscriber by id, including their email, name, lists and consent details.
Action
List newslettersReturns newsletter subscribers on your Pelcro site, optionally filtered by exact email address.
Action
Update customerUpdates an existing Pelcro customer's profile, such as contact details, marketing preferences, password and metadata. Fields left blank are left unchanged.
Action
Update NewsletterUpdates an existing newsletter subscriber's email, signup source, name, lists and consent details.
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 Condens
Condens to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Condens to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Condens to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Condens to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Condens to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Condens to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Pelcro
HubSpot to PelcroHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PelcroGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PelcroGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PelcroGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PelcroGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PelcroMailchimp marketing automation and email platform.
Questions
Condens and Pelcro, answered
What can start an automation from Condens?
Any of Condens's 2 triggers in the catalog, including Participant Created and Artifact Published. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pelcro when something happens in Condens?
Any of Pelcro's 12 actions, including Create Customer, Create Newsletter, Create Plan and Create Product. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pelcro to Condens?
Yes. When something happens in Pelcro, your agent can act in Condens too. This page covers both directions: Pelcro's triggers and Condens's actions are listed here as well.
Do I have to build a connector for Condens or Pelcro?
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 Condens and Pelcro 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.