Integration
Connect Pelcro to Signatureapi
When Customer Created fires in Pelcro, your agent runs Add ceremony in Signatureapi. 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 Signatureapi 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 can start in Signatureapi
When Customer Created in Pelcro
then Add ceremony in Signatureapi
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 Signatureapi
Triggers and actions 5 triggers · 27 actions
- Customer Created
Triggers 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.
- Customer Updated
Triggers when a customer is updated in Pelcro.
- Newsletter Created
Triggers when a new newsletter subscription is created in Pelcro.
- Newsletter Updated
Triggers when an existing Pelcro newsletter subscription is updated, such as a change to the subscriber's mailing lists or consent.
- Subscription Created
Triggers when a new subscription is created in Pelcro.
- Add address
Creates a new shipping, billing or primary address for a Pelcro customer.
- Add coupon
Creates a new discount coupon on your Pelcro site, with either a fixed amount or a percentage off.
- Create Customer
Creates a new customer on your Pelcro site.
- Create Newsletter
Creates a newsletter subscriber in Pelcro with their email, signup source and optional consent details.
- Create Plan
Creates a new pricing plan under a Pelcro product, setting its price, currency, billing interval and subscription behavior.
- Create Product
Creates a product in your Pelcro site. Plans and their prices are added under a product.
- Create Subscription
Creates a subscription for a Pelcro customer on a plan, optionally with a coupon, trial period or gift details.
- Get coupon
Returns a single coupon by id, including its code, discount, duration, redemption count and expiration.
- Get newsletter
Returns a single newsletter subscriber by id, including their email, name, lists and consent details.
- List newsletters
Returns newsletter subscribers on your Pelcro site, optionally filtered by exact email address.
- Update customer
Updates an existing Pelcro customer's profile, such as contact details, marketing preferences, password and metadata. Fields left blank are left unchanged.
- Update Newsletter
Updates an existing newsletter subscriber's email, signup source, name, lists and consent details.
- Add ceremony
Creates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.
- Add deliverable
Creates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.
- Add envelope
Creates an envelope with documents and recipients and starts the signing process.
- Add upload
Uploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.
- Cancel envelope
Cancel an in-progress envelope so remaining recipients can no longer sign.
- Delete envelope
Delete an envelope.
- Get deliverable
Retrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.
- Get envelope
Retrieve a single envelope by id.
- Get recipient
Retrieves a recipient's details, including status, ceremony information and completion timestamp.
- Get upload
Fetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.
- List deliverables
Returns the deliverables (signed PDFs with audit log) of an envelope, earliest first.
- List envelopes
Lists envelopes in the account, most recent first, optionally filtered by status or topic.
- Resend request
Resends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.
- Update envelope
Update mutable fields (e.g. title, metadata) of an existing envelope.
- Update recipient
Replaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.
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 Signatureapi
HubSpot to SignatureapiHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to SignatureapiGoogle Sheets
Gmail to SignatureapiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SignatureapiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pelcro and Signatureapi, 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 Signatureapi when something happens in Pelcro?
Any of Signatureapi's 15 actions, including Update envelope, Update recipient, Add ceremony and Add deliverable. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Signatureapi to Pelcro?
Signatureapi has no triggers in the catalog today, so automations start in Pelcro. If you need the other direction, ask: your agent reads Signatureapi's API documentation and adds it.
Do I have to build a connector for Pelcro or Signatureapi?
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 Signatureapi 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.