Integration
Connect Request Tracker (RT) to Fatture in Cloud
When Ticket Created fires in Request Tracker (RT), your agent runs Create Client in Fatture in Cloud. 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 Request Tracker (RT) and Fatture in Cloud 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)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 Request Tracker (RT) can start in Fatture in Cloud
When Ticket Created in Request Tracker (RT)
then Create Client in Fatture in Cloud
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 Request Tracker (RT) and Fatture in Cloud
Triggers and actions 3 triggers · 92 actions
- Ticket Correspondence
Triggers when a ticket is replied to (that is, corresponded with).
- Ticket Created
Triggers when a new Request Tracker ticket is created.
- Ticket Status Changed
Triggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
- Add asset
Create an asset.
- Add user
Create a user.
- Comment on a Ticket
Add an internal comment to a ticket and send to any internal watchers.
- Create Ticket
Create a new ticket in Request Tracker.
- Find Attachment
Locate an attachment by ID.
- Find Ticket
Locate a ticket by ID.
- Find Tickets
Issue a query to find matching tickets.
- Find Transaction
Find a transaction by ID
- Get asset
Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
- Get queue
Get a queue by id or name.
- Get user
Get a user by id or name.
- List queues
List all queues visible to user.
- List ticket history
List transactions of a ticket.
- Reply to a Ticket
Reply to the requestor and any internal or external watchers of a ticket.
- Update ticket
General ticket update (Owner, Priority, Queue, custom fields).
- Update Ticket Due Date
Update the due date of a ticket.
- Update Ticket Status
Update the status of a ticket.
- Update Ticket Subject
Update the subject of a ticket.
- Update user
Update a user.
- Create Cashbook Entry
Creates a new cashbook entry.
- Create Client
Creates a new client in a Fatture in Cloud company.
- Create F24
Creates a new F24 tax payment record in a Fatture in Cloud company.
- Create Issued Document
Creates a new issued document (invoice, quote, proforma, receipt, delivery note, credit note, order, work report, supplier order or self invoice) in a Fatture in Cloud company.
- Create Payment Account
Creates a new payment account.
- Create Payment Method
Creates a new payment method.
- Create Product
Creates a new product.
- Create Receipt
Creates a new receipt.
- Create Received Document
Creates a new document.
- Create Supplier
Creates a new supplier.
- Create Vat Type
Creates a vat type.
- Delete Bin Issued Document
Delete Bin Issued Document
- Delete Bin Received Document
Delete Bin Received Document
- Delete Cashbook Entry
Deletes the specified cashbook entry.
- Delete Client
Deletes the specified client.
- Delete F24
Removes the specified F24.
- Delete F24 Attachment
Removes the attachment of the specified F24.
- Delete Issued Document
Deletes the specified document.
- Delete Issued Document Attachment
Removes the attachment of the specified document.
- Delete Payment Account
Deletes the specified payment account.
- Delete Payment Method
Deletes the specified payment method.
- Delete Product
Deletes the specified product.
- Delete Receipt
Deletes the specified receipt.
- Delete Received Document
Deletes the specified document.
- Delete Supplier
Deletes the specified supplier.
- Delete Vat Type
Deletes the specified vat type.
- Get Archive Document
Gets the specified archive document.
- Get Bin Issued Documents List
Returns the issued documents currently in the bin.
- Get Bin Received Documents List
Get bin issued documents detail
- Get Cashbook Entry
Gets the specified cashbook entry.
- Get Client
Gets the specified client.
- Get F24
Gets the specified F24.
- Get Issued Document
Gets the specified document.
- Get Payment Account
Gets the specified payment account.
- Get Payment Method
Gets the specified payment method.
- Get Product
Gets the specified product.
- Get Receipt
Gets the specified receipt.
- Get Received Document
Gets the specified document.
- Get Supplier
Gets the specified supplier.
- Get Vat Type
Gets the specified vat type.
- Join Issued Documents
Joins issued documents.
- List Archive Documents
Lists the archive documents.
- List Cashbook Entries
Lists the cashbook entries.
- List Clients
Lists the clients.
- List F24
Lists the F24s.
- List Issued Documents
Lists the issued documents.
- List Payment Accounts
Lists the available payment accounts.
- List Payment Methods
Lists the available payment methods.
- List Pending Received Documents
Lists the pending received documents.
- List Products
Lists the products.
- List Receipts
Lists the receipts.
- List Received Documents
Lists the received documents.
- List Suppliers
Lists the suppliers.
- List Vat Types
Lists the available vat types.
- Modify Archive Document
Modifies the specified archive document.
- Modify Cashbook Entry
Modifies the specified cashbook entry.
- Modify Client
Modifies the specified client.
- Modify F24
Modifies the specified F24.
- Modify Issued Document
Modifies the specified document.
- Modify Payment Account
Modifies the specified payment account.
- Modify Payment Method
Modifies the specified payment method.
- Modify Product
Modifies the specified product.
- Modify Receipt
Modifies the specified receipt.
- Modify Received Document
Modifies the specified document.
- Modify Supplier
Modifies the specified supplier.
- Modify Vat Type
Modifies the specified vat type.
- Recover Issued Document From the Bin
Recover Issued Document From the Bin
- Recover Received Document From the Bin
Recover Received Document From the Bin
- Schedule Email
Schedules the sending of a document by email.
- Upload Archive Document Attachment
Uploads an attachment destined to an archive document. The actual association between the document and the attachment must be implemented separately, using the returned token.
- Upload F24 Attachment
Uploads an attachment destined to a F24. The actual association between the document and the attachment must be implemented separately, using the returned token.
- Upload Issued Document Attachment
Uploads an attachment destined to an issued document. The actual association between the document and the attachment must be implemented separately, using the returned token.
- Upload Received Document Attachment
Uploads an attachment destined to a received document. The actual association between the document and the attachment must be implemented separately, using the returned token.
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 Request Tracker (RT)
Request Tracker (RT) to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Request Tracker (RT) to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Request Tracker (RT) to StripeStripe is a payment processing platform for online businesses.
Request Tracker (RT) to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Request Tracker (RT) to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Request Tracker (RT) to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Fatture in Cloud
MINDBODY to Fatture in CloudMINDBODY is a powerful business management software that combines your scheduling, task automation...
HubSpot to Fatture in CloudHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Fatture in CloudGoogle Sheets
Gmail to Fatture in CloudGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Request Tracker (RT) and Fatture in Cloud, answered
What can start an automation from Request Tracker (RT)?
Any of Request Tracker (RT)'s 3 triggers in the catalog, including Ticket Created, Ticket Status Changed and Ticket Correspondence. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Fatture in Cloud when something happens in Request Tracker (RT)?
Any of Fatture in Cloud's 73 actions, including Create Cashbook Entry, Create Client, Create F24 and Create Issued Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fatture in Cloud to Request Tracker (RT)?
Fatture in Cloud has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads Fatture in Cloud's API documentation and adds it.
Do I have to build a connector for Request Tracker (RT) or Fatture in Cloud?
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 Request Tracker (RT) and Fatture in Cloud 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.