Integration
Connect Yay! Forms to Fergus
When something happens in Yay! Forms, your agent does the next thing in Fergus. Describe it 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 Yay! Forms and Fergus to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Yay! Forms can start in Fergus
When New Response in Yay! Forms
then Add Calendar Event in Fergus
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 Yay! Forms and Fergus
Triggers and actions 1 trigger · 43 actions
- New Response
Triggers when a new response is submitted.
- Create Field
Adds a new question field to a Yay! Forms form and returns the created field.
- Create Form
Creates a new form in a Yay! Forms workspace and returns the created form, including its ID and public key.
- Delete Field
Deletes one question field from a Yay! Forms form.
- Delete Form
Deletes a Yay! Forms form along with its fields and responses.
- Get Form
Returns one Yay! Forms form with its settings, theme, status and response counts.
- Get Form Stats
Returns view, start and response counts for a Yay! Forms form, plus its completion rate and average time to complete.
- List Fields
Returns every question field on a Yay! Forms form, in the order they appear.
- List Forms
Returns the forms in a Yay! Forms workspace, one page at a time.
- List Responses
Returns the responses submitted to a Yay! Forms form, one page at a time.
- List Workspaces
Returns the Yay! Forms workspaces you have access to, with each workspace's id, name and plan.
- Update Field
Updates one question field on a Yay! Forms form. Anything you leave blank keeps its current value.
- Update Form
Updates a Yay! Forms form's details and settings. Anything you leave blank keeps its current value.
- Add Calendar Event
Creates a new calendar event/booking.
- Add Contact
Creates a new contact.
- Add Note
Creates a new note against a record.
- Add Quote
Creates a new draft quote on a Fergus job. Supported for jobs whose job type is Quote or Estimate.
- Add Task
Creates a new task in Fergus, optionally linked to a job and assigned to employees.
- Archive Site
Archives a site in Fergus. The site can later be restored.
- Create Customer
Creates a new customer.
- Create Job
Creates a job in Fergus — an active job, a draft job, or a variation of an existing job.
- Create Site
Creates a new site.
- Delete Customer
Deletes a Fergus customer by ID.
- Edit Draft Job
Updates a draft job in Fergus. Only draft jobs can be edited; leave a field blank to keep its current value.
- Finalize Draft Job
Finalises a draft job in Fergus, turning it into an active job.
- Find All Quotes
Returns up to 100 quotes from across all jobs that match the specified status and date criteria.
- Find Customer
Returns the customers whose name, or main or billing contact's name, email or phone, contains the search text.
- Find Site
Finds sites by name, city, postal code, or free-text search. Returns the first page of matches (up to 10).
- Get Calendar Event
Returns a single Fergus calendar event by its ID, including title, start/end times, event type, assigned user, linked job/job phase and recurrence details.
- Get Contact
Returns a single Fergus contact (customer or site contact) by its ID, including name, position, company and contact items.
- Get Customer by ID
Returns a Fergus customer by its ID.
- Get Customer Invoice
Retrieves a customer invoice by ID.
- Get Job by ID
Retrieves a specific job using its unique ID.
- Get Quotes for Job
Returns all quotes for a Fergus job, optionally filtered by status.
- Get Site by ID
Retrieves a specific site using its unique ID.
- List Contacts
Lists contacts, with optional filtering.
- List Customer Invoices
Lists customer invoices, with optional filtering.
- List Notes
Returns the notes (with their replies) attached to a Fergus record.
- List Tasks
Lists the company's tasks, optionally filtered by status, assigned employee, job, due date range or overdue state.
- Update Contact
Updates an existing customer contact or site contact in Fergus.
- Update Customer
Updates an existing customer's details.
- Update Quote
Updates a draft quote on a Quote or Estimate job in Fergus: title, description and its sections with line items.
- Update Site
Updates an existing site's details.
- Update Task
Updates a task's description, due date, or assigned employees in Fergus. The job a task is linked to cannot be changed.
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 Yay! Forms
Yay! Forms to Google SheetsGoogle Sheets
Yay! Forms to NotionA new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.
Yay! Forms to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Yay! Forms to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Yay! Forms to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Yay! Forms to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
More into Fergus
HubSpot to FergusHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FergusSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FergusSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Gmail to FergusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FergusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Yay! Forms and Fergus, answered
What can start an automation from Yay! Forms?
Any of Yay! Forms's 1 trigger in the catalog, including New Response. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Fergus when something happens in Yay! Forms?
Any of Fergus's 31 actions, including Create Customer, Create Job, Create Site and Update Contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fergus to Yay! Forms?
Fergus has no triggers in the catalog today, so automations start in Yay! Forms. If you need the other direction, ask: your agent reads Fergus's API documentation and adds it.
Do I have to build a connector for Yay! Forms or Fergus?
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.
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.