Integration
Connect TestMonitor to Didit
When New Issue fires in TestMonitor, your agent runs Add user in Didit. 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 TestMonitor and Didit to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 TestMonitor can start in Didit
When New Issue in TestMonitor
then Add user in Didit
When New test case in TestMonitor
then Update user in Didit
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 TestMonitor and Didit
Triggers and actions 4 triggers · 31 actions
Trigger
New IssueTriggers when a new issue is added in the selected project.
Trigger
New test caseTrigger
New Test ResultTriggers when a new test result is created in the selected project.
Trigger
New test runAction
Add issue comment/issue/{issueId}/comments
Action
Add project/projects
Action
Add requirement/requirements
Action
Add test case/test-cases - create a test case.
Action
Add test result/test-results - create a test result.
Action
Create IssueCreates a new issue.
Action
Find an IssueFind an existing issue.
Action
Find a ProjectFind an existing project.
Action
Find a Test ResultFinds an existing test result.
Action
Find requirementsAction
Find test casesAction
Find test runsAction
List Issue CommentsReturns all comments posted on a TestMonitor issue.
Action
Update IssueUpdates an issue.
Action
Update test case/test-cases/{testCaseId}
Action
Update test result/test-results/{testResultId}
Action
Update test run/test-runs/{testRunId}
Action
Add businessCreate a Didit business (KYB) record.
Action
Add userCreate a Didit end-user record.
Action
Add webhook destinationRegister a webhook destination URL to receive Didit events.
Action
Create Verification SessionCreates a new Verification Session
Action
Delete verification sessionDelete a KYC or KYB verification session by id.
Action
Get businessRetrieve a Didit business record by vendor_data id.
Action
Get credit balanceRetrieve the account's remaining credit balance.
Action
Get userRetrieve a Didit end-user record by vendor_data id.
Action
List businessesList Didit business (KYB) records.
Action
List usersList Didit end-user records.
Action
List webhook destinationsList configured webhook destinations.
Action
Retrieve Verification SessionRetrieve a Verification Session
Action
Update businessUpdate a Didit business record.
Action
Update userUpdate a Didit end-user record.
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 TestMonitor
TestMonitor to DeskTimeDeskTime is automated time tracking software.
TestMonitor to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
TestMonitor to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
TestMonitor to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
TestMonitor to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
TestMonitor to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into Didit
HubSpot to DiditHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to DiditSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to DiditSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to DiditGoogle Sheets
Gmail to DiditGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to DiditGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
TestMonitor and Didit, answered
What can start an automation from TestMonitor?
Any of TestMonitor's 4 triggers in the catalog, including New Issue, New test case, New Test Result and New test run. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Didit when something happens in TestMonitor?
Any of Didit's 14 actions, including Create Verification Session, Update business, Update user and Add business. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Didit to TestMonitor?
Didit has no triggers in the catalog today, so automations start in TestMonitor. If you need the other direction, ask: your agent reads Didit's API documentation and adds it.
Do I have to build a connector for TestMonitor or Didit?
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.
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.