Integration
Connect FieldPulse to Way We Do
When New Job fires in FieldPulse, your agent runs Add a Checklist Comment in Way We Do. 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 FieldPulse and Way We Do 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 FieldPulse can start in Way We Do
When New Job in FieldPulse
then Add a Checklist Comment in Way We Do
When New Job in FieldPulse
then Add Collaborators in Way We Do
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 FieldPulse and Way We Do
Triggers and actions 1 trigger · 15 actions
Trigger
New JobTriggers when a new job is created in FieldPulse.
Action
Create JobCreates a new FieldPulse job for a customer.
Action
Get JobReturns one FieldPulse job by ID.
Action
Search JobsSearches FieldPulse jobs by term or status.
Action
Update JobUpdates a FieldPulse job.
Action
Add a Checklist CommentAdds a comment to a step of a running checklist instance.
Action
Add CollaboratorsAdds users or company roles as collaborators on a checklist instance.
Action
Find a Checklist by TitleFinds checklists whose title matches the search text.
Action
Find a Checklist Instance by IDReturns a checklist instance by its ID.
Action
Find a Checklist Instance by TitleFinds instances of a checklist whose title matches the search text.
Action
Find a Checklist Step by IDReturns one step of a checklist instance by its ID.
Action
Find a Checklist Step by TitleFinds steps of a checklist instance whose title matches the search text.
Action
Find a Procedure by TitleFinds standard procedures whose title matches the search text.
Action
Find a Procedure or Checklist by IDReturns a procedure or checklist by its ID.
Action
Find a UserFinds Way We Do users whose email or name matches the search text.
Action
Start Checklist InstanceStarts a new instance of a checklist, optionally assigning a user or role.
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 FieldPulse
FieldPulse to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
FieldPulse to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
FieldPulse to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
FieldPulse to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
FieldPulse to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
FieldPulse to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Way We Do
HubSpot to Way We DoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Way We DoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Way We DoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Way We DoGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Way We DoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Way We DoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
FieldPulse and Way We Do, answered
What can start an automation from FieldPulse?
Any of FieldPulse's 1 trigger in the catalog, including New Job. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Way We Do when something happens in FieldPulse?
Any of Way We Do's 11 actions, including Add a Checklist Comment, Add Collaborators, Find a Checklist by Title and Find a Checklist Instance by ID. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Way We Do to FieldPulse?
Way We Do has no triggers in the catalog today, so automations start in FieldPulse. If you need the other direction, ask: your agent reads Way We Do's API documentation and adds it.
Do I have to build a connector for FieldPulse or Way We Do?
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 FieldPulse and Way We Do 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.