Integration
Connect Testlify to QuintaDB
When something happens in Testlify, your agent does the next thing in QuintaDB. Describe it 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 Testlify and QuintaDB 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 Testlify can start in QuintaDB
When Candidate Stage Changed in Testlify
then Add form in QuintaDB
When Assessment Event in Testlify
then Create Record in QuintaDB
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 Testlify and QuintaDB
Triggers and actions 10 triggers · 10 actions
Trigger
Assessment EventFires when an assessment in the Testlify workspace is created, updated, archived or deleted.
Trigger
Candidate Stage ChangedFires when a candidate moves to a new stage in a Testlify assessment (invited, in progress, completed, disqualified or invitation expired).
Trigger
Test StatusFires when a candidate's test status changes in Testlify (invited, in progress, completed, disqualified or invitation expired).
Trigger
New DatabaseTriggers when a new database is created in the connected QuintaDB account.
Trigger
New FormTriggers when a new form is added to a QuintaDB database.
Trigger
New Form FieldTriggers when a new field is added to a QuintaDB form.
Trigger
New or Updated RecordTriggers when a record in a QuintaDB form is added or changed.
Trigger
New RecordTriggers when a new record is added to a QuintaDB form.
Trigger
New Table RecordTriggers when a new record is added to a QuintaDB form.
Trigger
New Table ReportTriggers when a new report is created on a QuintaDB form.
Action
Add formAdds a new form (table) to a QuintaDB database. Returns the created form.
Action
Create RecordAdds a new record to a QuintaDB form. The form's own fields are offered for mapping, and the created record's id is returned.
Action
Delete formDeletes a form (table) and its records from a QuintaDB database.
Action
Delete RecordDeletes a record from a QuintaDB form.
Action
Delete recordsDeletes several records from a QuintaDB form in one call.
Action
Find RecordsReturns the records in a QuintaDB form that match the conditions you specify.
Action
Get recordReturns one record from a QuintaDB form, including all of its field values.
Action
Update CellChanges the value of one field on one QuintaDB record.
Action
Update RecordChanges field values on an existing QuintaDB record. Fields you leave blank keep their current value.
Action
Upload fileUploads a file into a file field on an existing QuintaDB 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 Testlify
Testlify to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Testlify to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Testlify to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Testlify to Google SheetsGoogle Sheets
Testlify to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Testlify to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into QuintaDB
Dub to QuintaDBDub is the open-source link management infrastructure for modern marketing teams.
Pixabay to QuintaDBPixabay is a free image and video library. Search over 4 million royalty-free photos, illustrations, vector...
HubSpot to QuintaDBHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to QuintaDBGoogle Sheets
Gmail to QuintaDBGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QuintaDBGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Testlify and QuintaDB, answered
What can start an automation from Testlify?
Any of Testlify's 3 triggers in the catalog, including Candidate Stage Changed, Assessment Event and Test Status. Describe the moment in plain language and your agent picks the right one.
What can your agent do in QuintaDB when something happens in Testlify?
Any of QuintaDB's 10 actions, including Create Record, Update Cell, Update Record and Upload file. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from QuintaDB to Testlify?
QuintaDB has no triggers in the catalog today, so automations start in Testlify. If you need the other direction, ask: your agent reads QuintaDB's API documentation and adds it.
Do I have to build a connector for Testlify or QuintaDB?
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.