Integration
Connect Pelcro and Ventrata
When Customer Created fires in Pelcro, your agent runs Add booking in Ventrata, or Updated Booking in Ventrata to Create Customer in Pelcro. 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 Pelcro and Ventrata 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)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 Pelcro and Ventrata can do together
From Pelcro to Ventrata
When Customer Created in Pelcro
then Add booking in Ventrata
When Customer Updated in Pelcro
then Update booking in Ventrata
From Ventrata to Pelcro
When Updated Booking in Ventrata
then Create Customer in Pelcro
When Updated Booking in Ventrata
then Update customer in Pelcro
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 Pelcro and Ventrata
Triggers and actions 6 triggers · 23 actions
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.
Trigger
Updated BookingTriggers when any booking is created, updated, cancelled, or redeemed, including changes to customer details, products, options, quantities, or status.
Action
Add bookingReserves availability by creating an ON_HOLD booking. Confirm it afterwards with Confirm booking.
Action
Confirm booking/bookings/{uuid}/confirm - confirm an on-hold booking with contact details (OCTO Core).
Action
Delete booking/bookings/{uuid} - cancel a booking with optional reason (OCTO Core).
Action
Find availability/availability - search availability for a product/option over a date range or specific dates (OCTO Core).
Action
Find availability calendar/availability/calendar - daily availability summary for a product/option over a date range (OCTO Core).
Action
Find BookingFind bookings by reference, date, contact details or other filters. At least one primary filter is required.
Action
Get booking/bookings/{uuid} - retrieve a booking by UUID (OCTO Core).
Action
Get product/products/{id} - retrieve one product with its options and units (OCTO Core).
Action
Get supplierReturns the supplier the connected API key belongs to (name, reference, website, contact details).
Action
List products/products - list all bookable products for the supplier (OCTO Core).
Action
Update booking/bookings/{uuid} - amend an existing booking (date/time, units, contact) (OCTO Core).
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 Pelcro
Pelcro to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pelcro to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pelcro to StripeStripe is a payment processing platform for online businesses.
Pelcro to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pelcro to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pelcro to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Ventrata
HubSpot to VentrataHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to VentrataSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to VentrataSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to VentrataGoogle Sheets
Gmail to VentrataGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to VentrataGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pelcro and Ventrata, answered
What can start an automation from Pelcro?
Any of Pelcro's 5 triggers in the catalog, including Customer Created, Customer Updated, Newsletter Created and Newsletter Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ventrata when something happens in Pelcro?
Any of Ventrata's 11 actions, including Update booking, Add booking, Confirm booking and Find availability. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ventrata to Pelcro?
Yes. When something happens in Ventrata, your agent can act in Pelcro too. This page covers both directions: Ventrata's triggers and Pelcro's actions are listed here as well.
Do I have to build a connector for Pelcro or Ventrata?
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 Pelcro and Ventrata 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.