Integration
Connect Salesforce to Qase
When New object record fires in Salesforce, your agent runs Get project in Qase. 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 Salesforce and Qase 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)Salesforce holds the customer side of a problem — the Case, the account, the opportunity — while Qase holds the test cases, runs and defects. Connecting them lets a new or updated Salesforce record open a defect, start a test run or add a test case in Qase, and send Qase details back onto the Salesforce record so both teams read the same story.
Example flows
What Salesforce can start in Qase
When New object record in Salesforce
then Get project in Qase
When New or updated object record in Salesforce
then Add project in Qase
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 Salesforce and Qase
Triggers and actions 2 triggers · 36 actions
Trigger
New object recordPolling trigger: fires for each new record created in the specified SObject type. Polls SOQL ordered by CreatedDate descending.
Trigger
New or updated object recordPolling trigger: fires for each record created or modified in the specified SObject type. Polls SOQL ordered by SystemModstamp descending.
Action
Create object recordCreates a new record of the specified SObject type (standard or custom, e.g. Account, Contact, Lead, Opportunity, Case, or MyObject__c) with the supplied field values.
Action
Delete object recordDeletes an existing SObject record by object type and record ID.
Action
Describe objectReturns the full field and metadata description (describe) for an SObject type — useful for discovering available fields and their API names.
Action
Find most recent created or updated recordReturns the single most recently created or last-modified record for the specified SObject type (ordered by SystemModstamp DESC, LIMIT 1).
Action
Find object recordsFinds matching records for an SObject type by a field/value equality match via SOQL. Returns Id and the requested fields for all matches.
Action
Get object recordRetrieves a single SObject record by object type and record ID. Optionally restrict returned fields with a comma-separated 'fields' list.
Action
List objectsLists all available SObject types (standard and custom) on the org.
Action
SOQL queryExecutes a SOQL query against the org and returns matching records. Example: SELECT Id, Name FROM Account WHERE CreatedDate = TODAY.
Action
Update object recordUpdates an existing SObject record by object type and record ID with the supplied field values. Salesforce returns no body on success (HTTP 204).
Action
Add defectAdds a new defect to a Qase project.
Action
Add milestoneCreates a milestone in a Qase project.
Action
Add projectCreate a new project.
Action
Add runCreate a new test run in a project.
Action
Add test caseCreate a new test case in a project.
Action
Add test run resultCreate a result for a test run.
Action
Complete runMark a specific test run as completed.
Action
Delete projectDelete a project by code.
Action
Delete runDelete a test run by id.
Action
Delete test caseDelete a test case by id.
Action
Find entities by QQLSearches Qase test cases, defects, runs, results, plans or requirements with a Qase Query Language (QQL) expression.
Action
Get defectGet a specific defect by id.
Action
Get projectGet a project by its code.
Action
Get runRetrieves a specific test run in a Qase project, including its status, statistics, environment, milestone, tags and custom field values.
Action
Get test caseGet a specific test case by id.
Action
Get test run resultGet a test run result by hash code.
Action
List defectsReturns all defects in a Qase project, optionally filtered by status.
Action
List milestonesGet all milestones in a project.
Action
List projectsLists every project available to the connected Qase account.
Action
List runsGet all test runs in a project.
Action
List test casesGet all test cases in a project.
Action
List test run resultsGet all results for a project's test runs.
Action
Resolve defectMarks a specific defect in a Qase project as resolved.
Action
Update defectUpdate an existing defect.
Action
Update runUpdate a specific test run.
Action
Update test caseUpdates an existing test case in a Qase project. Only the fields you fill in are changed.
Action
Update test run resultUpdate a test run result.
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 Salesforce
Salesforce to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Salesforce to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Salesforce to StripeStripe is a payment processing platform for online businesses.
Salesforce to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Salesforce to NotionA new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.
Salesforce to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Qase
HubSpot to QaseHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to QaseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to QaseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to QaseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QaseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to QaseGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Salesforce and Qase, answered
Can something happening in Qase start one of these workflows?
No — the available Qase operations are actions only, so every workflow here begins with a Salesforce trigger such as a new record or a new or updated record. Qase then does the work: adding defects, runs, milestones, test cases, or updating and completing existing ones.
What if the Qase project or defect referred to on the Salesforce record is missing?
The agent can look it up first with Get project, Get defect or Find entities by QQL and only continue when the record is there. It tests every scenario, including the one where nothing matches, before the workflow is left running.
What can start an automation from Salesforce?
Any of Salesforce's 2 triggers in the catalog, including New object record and New or updated object record. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Qase when something happens in Salesforce?
Any of Qase's 27 actions, including Add run, Add test case, Complete run and Get project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qase to Salesforce?
Qase has no triggers in the catalog today, so automations start in Salesforce. If you need the other direction, ask: your agent reads Qase's API documentation and adds it.
Do I have to build a connector for Salesforce or Qase?
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 Salesforce and Qase 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.