Integration
Connect EasyPost to PractiTest
When New tracker update fires in EasyPost, your agent runs Add Issue in PractiTest. 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 EasyPost and PractiTest 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 EasyPost can start in PractiTest
When New tracker update in EasyPost
then Add Issue in PractiTest
When New tracker update in EasyPost
then Update Issue in PractiTest
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 EasyPost and PractiTest
Triggers and actions 1 trigger · 33 actions
Trigger
New tracker updateTriggers when EasyPost reports a tracker was created or updated, such as a new scan or status change on a package.
Action
Add addressCreates an address (a person, place or organization) in EasyPost, optionally verifying it for deliverability. Returns the saved address with any verification results.
Action
Add batchCreates a batch of shipments in EasyPost, so they can be bought, labelled, manifested or picked up together. A batch can also be created empty and shipments added later.
Action
Add pickupCreates a pickup request for a purchased shipment and returns the available pickup rates, which must then be bought to schedule the pickup.
Action
Add refundRequests refunds for one or more purchased shipping labels by carrier and tracking code, and returns the resulting refund records.
Action
Add shipmentCreates a shipment from a destination address, an origin address and a parcel, and returns the shipment with its available shipping rates.
Action
Add trackerCreates a tracker for a package tracking code (for labels bought outside EasyPost) and returns its current tracking status and history.
Action
Buy shipmentPurchases a shipping label for an existing shipment using the selected rate, returning the tracking code and postage label.
Action
Get addressReturns an address saved in EasyPost by its ID, including its verification results.
Action
Get batchReturns a batch of shipments, including its state, shipment statuses, consolidated label and scan form.
Action
Get pickupReturns a scheduled carrier pickup, including its status, confirmation number, address and available pickup rates.
Action
Get shipmentReturns a shipment, including its addresses, parcel, rates, label and tracking details.
Action
Add InstanceAdds a test to a test set in a PractiTest project as a new instance.
Action
Add IssueCreates an issue in a PractiTest project.
Action
Add TestCreate a new test case in a project.
Action
Create a RunUploads a new run result for a test instance in a PractiTest project — typically automated test results from CI, or a manual run with step results.
Action
Create RequirementCreates a new requirement.
Action
Delete IssueDeletes a specific issue from a PractiTest project.
Action
Delete RequirementDeletes a specific requirement from a PractiTest project.
Action
Delete TestDeletes a specific test from a PractiTest project.
Action
Get IssueRetrieves a single issue from a PractiTest project, including its attributes and custom field values.
Action
Get RequirementRetrieves a single requirement from a PractiTest project by its system id.
Action
Get RunRetrieve a single test run by id.
Action
Get TestRetrieve a single test by id.
Action
List InstancesLists the test instances in a PractiTest project, optionally filtered by test set, test, name or display id.
Action
List IssuesLists the issues in a PractiTest project, optionally narrowed by filter, display ids, title or PTQL query.
Action
List ProjectsLists the projects in the PractiTest account. With a personal API token, only the projects that user can access are returned.
Action
List RequirementsReturns all requirements in a PractiTest project, optionally narrowed by filter, display ids, name or PTQL query.
Action
List RunsList all test runs in a project.
Action
List TestsList all tests in a project.
Action
List UsersLists the users in the PractiTest account, optionally filtered by email address or to active users only.
Action
Update IssueUpdates an existing issue in a PractiTest project. Only the fields you fill in are changed.
Action
Update RequirementUpdate a requirement's fields.
Action
Update TestUpdates a specific test in a PractiTest project. Only the fields you fill in are changed.
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 EasyPost
EasyPost to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
EasyPost to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
EasyPost to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
EasyPost to Google SheetsGoogle Sheets
EasyPost to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
EasyPost to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into PractiTest
HubSpot to PractiTestHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PractiTestSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PractiTestSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PractiTestGoogle Sheets
Gmail to PractiTestGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PractiTestGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
EasyPost and PractiTest, answered
What can start an automation from EasyPost?
Any of EasyPost's 1 trigger in the catalog, including New tracker update. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PractiTest when something happens in EasyPost?
Any of PractiTest's 22 actions, including Create a Run, Create Requirement, Update Issue and Update Requirement. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PractiTest to EasyPost?
PractiTest has no triggers in the catalog today, so automations start in EasyPost. If you need the other direction, ask: your agent reads PractiTest's API documentation and adds it.
Do I have to build a connector for EasyPost or PractiTest?
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.