Integration
Connect Document360 and TicketCo
When New Article fires in Document360, your agent runs Find Customers in TicketCo, or New Event in TicketCo to List Project Versions in Document360. 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 Document360 and TicketCo 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 Document360 and TicketCo can do together
From Document360 to TicketCo
When New Article in Document360
then Find Customers in TicketCo
From TicketCo to Document360
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 Document360 and TicketCo
Triggers and actions 3 triggers · 14 actions
- New Article
Triggers when a new article is added to a Document360 project version.
- Create Article
Creates a new article in a Document360 project version and returns its ID.
- Create Category
Creates a category in a project version and returns its ID.
- Delete Article
Deletes an article from the knowledge base.
- Get Article
Returns one article's content and details in the given language.
- List Articles
Returns the articles in a project version.
- List Categories
Returns the categories in a project version.
- List Project Versions
Returns the knowledge base's project versions (workspaces) with their IDs.
- Update Article
Updates an article's title, content or category in the given language.
- New Event
Triggers when a new event appears in your TicketCo account.
- New Transaction
Triggers when a new ticket transaction is recorded in TicketCo.
- Find Customers
Returns TicketCo customers, optionally filtered by email, ID or last update time.
- Get Event
Returns one TicketCo event by its ID, with its title, location, dates, prices and ticket types.
- Get Event Status
Returns the current status of one TicketCo event.
- Get Membership
Returns one TicketCo membership with its members.
- List Events
Returns the organizer's active and ended TicketCo events, filterable by title, type, location, status and start date.
- List Transactions
Returns TicketCo ticket transactions, filterable by event, customer, buyer email, invoice and reference number.
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 Document360
Document360 to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Document360 to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Document360 to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Document360 to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Document360 to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Document360 to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into TicketCo
Questions
Document360 and TicketCo, answered
What can start an automation from Document360?
Any of Document360's 1 trigger in the catalog, including New Article. Describe the moment in plain language and your agent picks the right one.
What can your agent do in TicketCo when something happens in Document360?
Any of TicketCo's 6 actions, including Find Customers, Get Event, Get Event Status and Get Membership. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from TicketCo to Document360?
Yes. When something happens in TicketCo, your agent can act in Document360 too. This page covers both directions: TicketCo's triggers and Document360's actions are listed here as well.
Do I have to build a connector for Document360 or TicketCo?
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 Document360 and TicketCo 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.