Integration
Connect Targetprocess to HitPay
When New Bug fires in Targetprocess, your agent runs Add customer in HitPay. 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 Targetprocess and HitPay 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 Targetprocess can start in HitPay
When New Bug in Targetprocess
then Add customer in HitPay
When New Build in Targetprocess
then Add order in HitPay
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 Targetprocess and HitPay
Triggers and actions 11 triggers · 30 actions
Trigger
New BugTriggers when a new Bug is added in Targetprocess.
Trigger
New BuildTriggers when a new Build is added in Targetprocess.
Trigger
New CommentTriggers when a new Comment is added in Targetprocess.
Trigger
New FeatureTriggers when a new Feature is added in Targetprocess.
Trigger
New IterationTriggers when a new Iteration is added in Targetprocess.
Trigger
New ReleaseTriggers when a new Release is added in Targetprocess.
Trigger
New RequestTriggers when a new Request is added in Targetprocess.
Trigger
New TaskTriggers when a new Task is added in Targetprocess.
Trigger
New Team IterationTriggers when a new Team Iteration is added in Targetprocess.
Trigger
New TimeTriggers when a new Time record is added in Targetprocess.
Trigger
New User StoryTriggers when a new User Story is added in Targetprocess.
Action
Add Requester to RequestCreates a Requester and attaches them to an existing Request.
Action
Change StateChanges the workflow state of an existing entity.
Action
Create BugCreates a new Bug in a Targetprocess project.
Action
Create BuildCreates a Build in a Targetprocess project.
Action
Create FeatureCreates a Feature, a high-level requirement that groups User Stories.
Action
Create RequestCreates a Request (an idea, issue or question from users).
Action
Create TaskCreates a Task under an existing User Story.
Action
Create User StoryCreates a User Story in a project.
Action
Add customerCreates a customer in your HitPay account with their contact details and optional address.
Action
Add orderCreates a new draft order in HitPay.
Action
Add subscription planCreates a subscription plan with a name, amount and billing frequency that customers can be signed up to for recurring billing.
Action
Create Payment RequestCreates a HitPay payment request and returns its checkout link for the buyer to pay.
Action
Delete customerDeletes a customer from your HitPay account.
Action
Delete invoiceDeletes an invoice from your HitPay business account.
Action
Delete Payment RequestDeletes a payment request. Completed payment requests cannot be deleted.
Action
Delete productDeletes a product from your HitPay product catalog.
Action
Get balancesReturns your HitPay account balances for each currency, including available, pending and reserve amounts.
Action
Get chargeReturns the details of a single HitPay charge, including amount, fees, status, payment method, customer and refunds.
Action
Get customerReturns the details of a HitPay customer, including contact information and address.
Action
Get orderReturns the full details of a HitPay order, including its line items, charges, customer and totals.
Action
Get Payment Request DetailsReturns a payment request's details and status, including its amount, customer, checkout URL and any payments made against it.
Action
Get productReturns the details of a product, including its price, variations and images.
Action
List chargesReturns the charges (payments) on your HitPay account, optionally filtered by status, date, amount, customer, payment request or payout.
Action
List customersReturns all customers saved in your HitPay account.
Action
List invoicesReturns the invoices in your HitPay account, optionally filtered by customer email, status or reference.
Action
List payoutsReturns payouts of your HitPay balance to your linked bank account, newest first, optionally filtered by status and creation date.
Action
List productsReturns the products in your HitPay account, optionally filtered by status, category, source, inventory, location, channel or keyword.
Action
Refund PaymentRefunds all or part of a successful payment, returning the refund record.
Action
Update customerUpdates an existing customer's details, such as name, email, phone and address.
Action
Update productUpdates an existing product in your HitPay store, such as its name, price, stock, categories and variations.
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 Targetprocess
Targetprocess to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Targetprocess to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Targetprocess to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Targetprocess to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Targetprocess to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Targetprocess to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
More into HitPay
HubSpot to HitPayHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to HitPaySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to HitPaySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HitPayGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to HitPayGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HitPayGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Targetprocess and HitPay, answered
What can start an automation from Targetprocess?
Any of Targetprocess's 11 triggers in the catalog, including New Bug, New Build, New Comment and New Feature. Describe the moment in plain language and your agent picks the right one.
What can your agent do in HitPay when something happens in Targetprocess?
Any of HitPay's 22 actions, including Create Payment Request, Update customer, Update product and Add customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from HitPay to Targetprocess?
HitPay has no triggers in the catalog today, so automations start in Targetprocess. If you need the other direction, ask: your agent reads HitPay's API documentation and adds it.
Do I have to build a connector for Targetprocess or HitPay?
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 Targetprocess and HitPay 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.