Integration
Connect Intulse and Jetdocs
When Queue Event Created fires in Intulse, your agent runs Get Ticket in Jetdocs, or New Comment in Jetdocs to Add contact in Intulse. 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 Intulse and Jetdocs 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 Intulse and Jetdocs can do together
From Intulse to Jetdocs
When Queue Event Created in Intulse
then Get Ticket in Jetdocs
When Text Message Received in Intulse
then List Tickets in Jetdocs
From Jetdocs to Intulse
When New Comment in Jetdocs
then Add contact in Intulse
When New Ticket in Jetdocs
then Send Text Message in Intulse
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 Intulse and Jetdocs
Triggers and actions 9 triggers · 21 actions
Trigger
Call EndedTriggers when a call in your Intulse organization ends and appears in the call log.
Trigger
Queue Event CreatedTriggers when a new event happens in one of your Intulse call queues.
Trigger
Text Message ReceivedTriggers when a new SMS/MMS text message appears in your Intulse organization.
Action
Add contactCreates a new user contact in Intulse with name, company, phone numbers and emails.
Action
Delete contactDeletes a user contact from Intulse.
Action
Get extensionReturns one phone extension with its name, device state, and Do Not Disturb, call waiting and call forwarding status.
Action
Get userReturns a specific Intulse user by ID, including name, email, mobile, extension and admin status.
Action
List callsReturns the organization's calls that started within a date range, optionally narrowed by an advanced filter. Requires a master API key.
Action
List extensionsReturns every extension configured in your Intulse account, with its name, device state and DND, call waiting and call forwarding status. Requires an admin user or organization API key.
Action
List queuesReturns the call queues in your Intulse organization with their live stats, members and waiting callers.
Action
List usersReturns the users in your Intulse organization, with their names, email, mobile number, extension and admin status.
Action
List voicemailsReturns every voicemail box in your organization with its folders and messages, including caller, duration, date and transcription.
Action
Originate CallStarts a phone call from an Intulse extension to a target number.
Action
Send Text MessageSends an SMS text message from one of your Intulse numbers.
Action
Update contactUpdates an existing user contact in Intulse, such as its name, company, phone numbers, emails and notes.
Action
Update Extension Call Forward AlwaysTurns Call Forward Always on or off for an Intulse extension and sets where calls forward to.
Action
Update Extension DNDTurns Do-Not-Disturb on or off for an Intulse extension.
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.
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 Intulse
Intulse to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Intulse to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Intulse to MailchimpMailchimp marketing automation and email platform.
Intulse to StripeStripe is a payment processing platform for online businesses.
Intulse to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Intulse to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Jetdocs
HubSpot to JetdocsHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to JetdocsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to JetdocsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to JetdocsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to JetdocsGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to JetdocsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Intulse and Jetdocs, answered
What can start an automation from Intulse?
Any of Intulse's 3 triggers in the catalog, including Queue Event Created, Text Message Received and Call Ended. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Jetdocs when something happens in Intulse?
Any of Jetdocs's 7 actions, including Get Ticket, List Categories, List Templates and List Tickets. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Jetdocs to Intulse?
Yes. When something happens in Jetdocs, your agent can act in Intulse too. This page covers both directions: Jetdocs's triggers and Intulse's actions are listed here as well.
Do I have to build a connector for Intulse or Jetdocs?
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 Intulse and Jetdocs 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.