Integration
Connect FieldPulse and Textellent
When New Job fires in FieldPulse, your agent runs Add Contact in Textellent, or Contact Added To Tag in Textellent to Create Job in FieldPulse. 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 Textellent 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 and Textellent can do together
From FieldPulse to Textellent
When New Job in FieldPulse
then Add Contact in Textellent
When New Job in FieldPulse
then Assign Contact To Tag in Textellent
From Textellent to FieldPulse
When Contact Added To Tag in Textellent
then Create Job in FieldPulse
When New Contact in Textellent
then Update Job in FieldPulse
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 Textellent
Triggers and actions 5 triggers · 13 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.
Trigger
Contact Added To TagTriggers when a contact is added to a tag.
Trigger
Contact Removed From TagTriggers when a contact is removed from a tag.
Trigger
New ContactTriggers when a new contact is added in Textellent.
Trigger
Phone Number Added To Do Not TextTriggers when a phone number is added to the Do Not Text list.
Action
Add ContactCreates a contact in Textellent with name, phone numbers, email, tags and notes.
Action
Assign Contact To TagAssigns a contact, by phone number, to a Textellent tag.
Action
Create TagCreates a Textellent contact tag.
Action
Delete TagDeletes a Textellent contact tag.
Action
Get ContactReturns one Textellent contact by its ID.
Action
Get TagReturns one Textellent contact tag by its ID.
Action
List TagsReturns all Textellent contact tags.
Action
Remove Contact From TagRemoves contacts, by phone number, from a Textellent tag.
Action
Update TagUpdates a Textellent contact tag.
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 Textellent
HubSpot to TextellentHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TextellentSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TextellentSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TextellentGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TextellentGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TextellentGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
FieldPulse and Textellent, 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 Textellent when something happens in FieldPulse?
Any of Textellent's 9 actions, including Create Tag, Update Tag, Add Contact and Assign Contact To Tag. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Textellent to FieldPulse?
Yes. When something happens in Textellent, your agent can act in FieldPulse too. This page covers both directions: Textellent's triggers and FieldPulse's actions are listed here as well.
Do I have to build a connector for FieldPulse or Textellent?
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 Textellent 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.