Integration

Connect RunSignup to FormAPI

When New Donation fires in RunSignup, your agent runs Add folder in FormAPI. Describe the whole flow and it is built, tested on every scenario and kept running.

RunSignup5 triggers RunSignup10 actions FormAPI10 actions

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 RunSignup and FormAPI to do together?

Ask the assistant

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide

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

Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide

Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide

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

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

Example flows

What RunSignup can start in FormAPI

When New Donation in RunSignupthen Add folder in FormAPI
When New Fundraiser in RunSignupthen Generate PDF in FormAPI

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 RunSignup and FormAPI

Triggers and actions 5 triggers · 20 actions

Trigger
New Donation
Triggers when a new donation is made to the selected race.
Trigger
New Fundraiser
Triggers when a new fundraiser is created for the selected race.
Trigger
New Participant Registration
Triggers when a new participant registers for the selected event of a race.
Trigger
Removed Participant Registration
Triggers when a participant's registration is removed, refunded, transferred or deferred from the selected event of a race.
Trigger
Updated Fundraiser
Triggers when an existing fundraiser for the selected race is updated.
Action
Find Fundraiser by ID
Finds a race fundraiser by its ID, including the amount raised and number of donations.
Action
Get Participant Counts for a Race (All Events)
Returns the number of current participants in every event of a race.
Action
Get Participant Counts for a Race (Single Event Only)
Returns the number of current participants in one event of a race.
Action
Get race
Returns a RunSignup race's details: name, dates, location, URL and its events, with optional waivers, questions, add-ons, pricing and other settings.
Action
Get race results
Returns the finishing results for a race event, grouped by result set, with optional filters by name, gender, bib, place, age and location.
Action
List coupons
Returns the coupons set up for a RunSignup race, optionally filtered by code, availability or creation date.
Action
List donations
Returns the donations made to a RunSignup race, newest first.
Action
List participants
Returns the participants registered for one or more events in a RunSignup race, including user details, registration date and payment information.
Action
List races
Returns RunSignup races, optionally filtered by name, date range, location, event type and distance.
Action
List teams
Returns the groups/teams registered for a RunSignup race event.
Action
Add folder
Creates a new folder in DocSpring for organizing templates.
Action
Delete submission
Expire/delete a PDF submission so it is no longer downloadable.
Action
Generate PDF
Fill a PDF template with field data and generate a submission.
Action
Get combined submission
Checks the status of a combined submission (merged PDFs) and returns its download URL once processed.
Action
Get data request
Look up a submission data request (e.g. an e-signature request) by id.
Action
Get submission
Checks the status of a generated PDF submission and returns its details, including the download URL once processed.
Action
Get template
Looks up a DocSpring PDF template and returns its settings and document processing status.
Action
List folders
Lists the folders in the DocSpring account, optionally only those inside a given parent folder.
Action
Merge PDFs
Merges submission PDFs, template PDFs, custom files, other merged PDFs or PDFs at a URL into one combined PDF. The merge runs asynchronously; use Get combined submission to check when the download URL is ready.
Action
Request signature
Creates a PDF submission from a template and sends one person a request to fill in and sign their fields. The PDF is generated once they complete it.

Each app on its own

Reviews

What our customers say

More into FormAPI

Questions

RunSignup and FormAPI, answered

What can start an automation from RunSignup?

Any of RunSignup's 5 triggers in the catalog, including New Donation, New Fundraiser, New Participant Registration and Removed Participant Registration. Describe the moment in plain language and your agent picks the right one.

What can your agent do in FormAPI when something happens in RunSignup?

Any of FormAPI's 10 actions, including Add folder, Generate PDF, Get combined submission and Get data request. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from FormAPI to RunSignup?

FormAPI has no triggers in the catalog today, so automations start in RunSignup. If you need the other direction, ask: your agent reads FormAPI's API documentation and adds it.

Do I have to build a connector for RunSignup or FormAPI?

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 RunSignup and FormAPI 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.

Connect RunSignup to FormAPI

What do you want RunSignup and FormAPI to do together?

What RunSignup can start in FormAPI

Triggers and actions 5 triggers · 20 actions

Each app on its own

What our customers say

More from RunSignup

More into FormAPI

RunSignup and FormAPI, answered

What can start an automation from RunSignup?

What can your agent do in FormAPI when something happens in RunSignup?

Can it also run from FormAPI to RunSignup?

Do I have to build a connector for RunSignup or FormAPI?

Can my AI client use RunSignup and FormAPI without building an automation?

What happens when something fails?

Is there a free plan?