Integration
Connect Jetdocs and Text In Church
When New Comment fires in Jetdocs, your agent runs Add comment in Text In Church, or Connect Card Submitted in Text In Church to Get Ticket in Jetdocs. 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 Jetdocs and Text In Church 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 Jetdocs and Text In Church can do together
From Jetdocs to Text In Church
When New Comment in Jetdocs
then Add comment in Text In Church
When New Ticket in Jetdocs
then Create Task in Text In Church
From Text In Church to Jetdocs
When Connect Card Submitted in Text In Church
then Get Ticket in Jetdocs
When Person Created in Text In Church
then List Tickets in Jetdocs
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 Jetdocs and Text In Church
Triggers and actions 9 triggers · 26 actions
Trigger
New CommentTriggers when a comment is added to a ticket.
Trigger
New TicketTriggers when a new ticket is submitted.
Trigger
Ticket EditTriggers when a ticket's submitted form answers are edited.
Trigger
Ticket ReassignTriggers when a ticket is reassigned to a new responder.
Trigger
Ticket Status ChangeTriggers when a ticket's status changes (for example from Outstanding to Completed).
Trigger
Workflow UpdateTriggers when a ticket's workflow steps are approved, rejected or otherwise updated.
Action
Get TicketReturns one ticket by its ID, with its form answers, workflow steps and history.
Action
List CategoriesReturns the organization's request categories.
Action
List TemplatesReturns the organization's request templates with their form fields and workflow steps.
Action
List TicketsReturns tickets submitted in the organization, newest first, optionally filtered by template or status.
Action
List User GroupsReturns the organization's user groups across all workspaces, with member emails.
Action
List UsersReturns the organization's users with their role and seat status.
Action
List WorkspacesReturns the organization's workspaces with their settings and members.
Trigger
Connect Card SubmittedTriggers when someone submits a connect card in Text In Church.
Trigger
Person CreatedTriggers when a new person is added to Text In Church.
Trigger
Person Joined GroupTriggers when a person joins a group in Text In Church.
Action
Add commentAdds a comment to a person's record in Text In Church.
Action
Add groupCreates a new group in Text In Church.
Action
Add to GroupAdds a person to a group in Text In Church.
Action
Create TaskCreates a task in Text In Church assigned to a specific user.
Action
Create/Update PersonCreates a new person in Text In Church, or updates an existing person when their hash is given.
Action
Delete groupDeletes a group from your Text In Church account.
Action
Delete personDeletes a person (contact) from your Text In Church account.
Action
Find GroupFinds a group in Text In Church by its name.
Action
Find PersonFinds people in Text In Church by email, phone or a name search.
Action
Get CommentsReturns the comments recorded on a person in Text In Church.
Action
Get groupReturns a single group, looked up by its hash.
Action
Get message statusReturns the delivery status of a sent message for one recipient, looked up by its receipt.
Action
Get PersonReturns one person's record from Text In Church by their hash.
Action
List contact custom columnsReturns the custom contact columns (fields) defined on the Text In Church account, optionally filtered by name or type.
Action
List conversationsReturns text conversations in your Text In Church account, optionally filtered by person, group, read or archived status.
Action
List messagesReturns text and email messages in your Text In Church account, optionally filtered by contact, group, conversation, date range, type or search term.
Action
Remove From GroupRemoves a person from a group in Text In Church.
Action
Send Text MessageSends a text message to a person or a group in Text In Church, now or at a scheduled time.
Action
Update groupUpdates an existing group's name, type, sharing, keyword auto-reply, form confirmation and sync settings. Fields left blank are not 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 Jetdocs
Jetdocs to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Jetdocs to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Jetdocs to MailchimpMailchimp marketing automation and email platform.
Jetdocs to StripeStripe is a payment processing platform for online businesses.
Jetdocs to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Jetdocs to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Text In Church
HubSpot to Text In ChurchHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Text In ChurchSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Text In ChurchSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Text In ChurchGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Text In ChurchGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Text In ChurchGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Jetdocs and Text In Church, answered
What can start an automation from Jetdocs?
Any of Jetdocs's 6 triggers in the catalog, including New Comment, New Ticket, Ticket Edit and Ticket Reassign. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Text In Church when something happens in Jetdocs?
Any of Text In Church's 19 actions, including Create Task, Create/Update Person, Send Text Message and Update group. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Text In Church to Jetdocs?
Yes. When something happens in Text In Church, your agent can act in Jetdocs too. This page covers both directions: Text In Church's triggers and Jetdocs's actions are listed here as well.
Do I have to build a connector for Jetdocs or Text In Church?
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 Jetdocs and Text In Church 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.