Integration
Connect WaiverForever to Code::Stats
When New Waiver Accepted fires in WaiverForever, your agent runs Get user in Code::Stats. 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 WaiverForever and Code::Stats 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 WaiverForever can start in Code::Stats
When New Waiver Accepted in WaiverForever
then Get user in Code::Stats
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 WaiverForever and Code::Stats
Triggers and actions 2 triggers · 11 actions
- New Waiver Accepted
Triggers when a signed waiver is accepted (approved), optionally for one template.
- New Waiver Submitted
Triggers when a new waiver is signed and submitted, optionally for one template.
- Accept Waiver
Accepts a waiver that is in pending status.
- Create Request Group
Creates a waiver request group for a template and returns its shareable signing link.
- Create Tracking Waiver Request
Creates a one-off signing link for a template and returns the link plus a tracking ID.
- Find Waivers
Searches signed waivers by keyword, template, status, reference number or signing date range.
- Get Request Group
Returns one waiver request group, optionally with the waivers signed against it.
- Get Waiver
Returns one signed waiver, including its field answers, status and PDF link.
- List Request Groups
Returns the waiver request groups for a template, optionally filtered by name or status.
- List Templates
Returns every waiver template in the WaiverForever account.
- Update Request Group
Updates a waiver request group's name, size, note or contact info.
- Update Waiver Note
Sets the note on a signed waiver.
- Get user
Retrieve a public user's profile (total XP, new XP in last 12h, per-machine, per-language and per-date XP).
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 WaiverForever
WaiverForever to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
WaiverForever to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
WaiverForever to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
WaiverForever to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
WaiverForever to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
WaiverForever to AnthropicAnthropic builds Claude, a family of large language models.
More into Code::Stats
HubSpot to Code::StatsHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Code::StatsSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Code::StatsSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Code::StatsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Code::StatsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Code::StatsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
WaiverForever and Code::Stats, answered
What can start an automation from WaiverForever?
Any of WaiverForever's 2 triggers in the catalog, including New Waiver Accepted and New Waiver Submitted. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Code::Stats when something happens in WaiverForever?
Any of Code::Stats's 1 action, including Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Code::Stats to WaiverForever?
Code::Stats has no triggers in the catalog today, so automations start in WaiverForever. If you need the other direction, ask: your agent reads Code::Stats's API documentation and adds it.
Do I have to build a connector for WaiverForever or Code::Stats?
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 WaiverForever and Code::Stats 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.