Integration
Connect Clientary and RunSignup
When New Expense fires in Clientary, your agent runs Get Participant Counts for a Race (All Events) in RunSignup, or New Donation in RunSignup to Add contact in Clientary. 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 Clientary and RunSignup 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 Clientary and RunSignup can do together
From Clientary to RunSignup
When New Expense in Clientary
then Get Participant Counts for a Race (All Events) in RunSignup
From RunSignup to Clientary
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 Clientary and RunSignup
Triggers and actions 8 triggers · 24 actions
- New Expense
Triggers when a new expense is recorded in your Clientary account during the current fiscal year.
- New Invoice
Triggers when a new invoice is created in Clientary, optionally limited to invoices in a given status or matching a search.
- New Staff
Triggers when a new staff user is added to your Clientary account.
- Add comment
Posts a comment on an invoice, estimate, project, task, proposal or contract and notifies the people involved.
- Add contact
Creates a new contact (an individual person) under an existing Clientary client.
- Add contract
Creates a contract for a client in Clientary, optionally starting from a contract template, with its sections and signers.
- Add proposal
Creates a proposal for a client in Clientary, optionally starting from a proposal template, with its sections and signers.
- Add retainer
Creates a retainer for a client in Clientary: an up-front payment request kept apart from ordinary invoices.
- Client
Creates a new client in Clientary with its name, address, tax id, website and description.
- Create Estimate
Creates an estimate in Clientary, optionally for a client, with its dates, taxes, notes and line items.
- Create Invoice
Creates an invoice in Clientary, optionally for a client, with dates, currency, taxes, notes and line items.
- Create Lead
Creates a new lead (a prospective client) in Clientary.
- Create Task
Creates a new task (a to-do item) in Clientary, optionally on a project and assigned to a staff member.
- Expense
Creates a new expense in Clientary, optionally assigned to a client or project.
- Get client
Returns a single Clientary client by its ID, including its contact and address details.
- List comments
Returns the comments on one Clientary invoice, estimate, project, task, proposal or contract, newest first.
- Update contract
Updates an existing Clientary contract: its subject, date, client, status, signers or sections. Only a draft contract can be changed; void and reopen a sent contract first.
- New Donation
Triggers when a new donation is made to the selected race.
- New Fundraiser
Triggers when a new fundraiser is created for the selected race.
- New Participant Registration
Triggers when a new participant registers for the selected event of a race.
- Removed Participant Registration
Triggers when a participant's registration is removed, refunded, transferred or deferred from the selected event of a race.
- Updated Fundraiser
Triggers when an existing fundraiser for the selected race is updated.
- Find Fundraiser by ID
Finds a race fundraiser by its ID, including the amount raised and number of donations.
- Get Participant Counts for a Race (All Events)
Returns the number of current participants in every event of a race.
- Get Participant Counts for a Race (Single Event Only)
Returns the number of current participants in one event of a race.
- 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.
- 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.
- List coupons
Returns the coupons set up for a RunSignup race, optionally filtered by code, availability or creation date.
- List donations
Returns the donations made to a RunSignup race, newest first.
- List participants
Returns the participants registered for one or more events in a RunSignup race, including user details, registration date and payment information.
- List races
Returns RunSignup races, optionally filtered by name, date range, location, event type and distance.
- List teams
Returns the groups/teams registered for a RunSignup race event.
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 Clientary
Clientary to ViaCepViaCep is a Brazilian postal code (CEP) lookup service.
Clientary to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clientary to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clientary to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Clientary to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Clientary to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into RunSignup
Google Calendar to RunSignupGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to RunSignupGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to RunSignupMailchimp marketing automation and email platform.
Questions
Clientary and RunSignup, answered
What can start an automation from Clientary?
Any of Clientary's 3 triggers in the catalog, including New Expense, New Invoice and New Staff. Describe the moment in plain language and your agent picks the right one.
What can your agent do in RunSignup when something happens in Clientary?
Any of RunSignup's 10 actions, including Find Fundraiser by ID, Get Participant Counts for a Race (All Events), Get Participant Counts for a Race (Single Event Only) and Get race. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from RunSignup to Clientary?
Yes. When something happens in RunSignup, your agent can act in Clientary too. This page covers both directions: RunSignup's triggers and Clientary's actions are listed here as well.
Do I have to build a connector for Clientary or RunSignup?
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 Clientary and RunSignup 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.