Integration
Connect Hero Parser to Retailed
When New Candidate fires in Hero Parser, your agent runs Find Goat products in Retailed. 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 Hero Parser and Retailed 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 Hero Parser can start in Retailed
When New Candidate in Hero Parser
then Find Goat products in Retailed
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 Hero Parser and Retailed
Triggers and actions 2 triggers · 21 actions
- New Candidate
Triggers when a new candidate is created (CV parsed).
- New Recruitment
Triggers when a new recruitment is created.
- Create Recruitment
Create a Recruitment in the system.
- Delete resumes
Delete resumes for a recruitment.
- Get candidate
Get candidate details by id.
- Get recruitment
Get recruitment details by id.
- List candidates
Get list of candidates by recruitment.
- List recruitments
Get the recruitments list.
- List resumes
Get list of resumes by recruitment.
- Process resumes
Process selected resumes for a recruitment (AI parsing).
- Send candidate feedback
Send feedback to selected candidates.
- Update candidate status
Change status for selected candidates.
- Update recruitment
Edit an existing recruitment.
- Upload CV
Upload a CV to existing recruitment.
- Find Goat products
Searches GOAT for products matching a SKU or product name and returns the matching products.
- Find prices in database
Finds price records in the Retailed database for a product, by SKU or product id, optionally limited to certain sizes.
- Find products in database
Finds products in the Retailed database by SKU, product id, source or UPC/EAN barcode.
- Find StockX products
Searches StockX for products by name, brand or SKU and returns the matching products.
- Find variants in database
Finds product variants in the Retailed database by UPC/EAN barcode or category, returning titles, brands, sizes and linked marketplace products.
- Get API usage
Returns your Retailed API plan name and the number of requests remaining.
- Get Goat prices
Returns the latest GOAT prices for a product, broken down by size and condition.
- Get Goat product
Returns the details of a GOAT product — name, SKU, brand, release date, sizes, pictures and prices — from its product URL or slug.
- Get StockX product
Returns a StockX product's details, including name, SKU, brand, size variants and current market asks, bids and sales.
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 Hero Parser
Hero Parser to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Hero Parser to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Hero Parser to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Hero Parser to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Hero Parser to MailchimpMailchimp marketing automation and email platform.
Hero Parser to StripeStripe is a payment processing platform for online businesses.
More into Retailed
Google Sheets to RetailedGoogle Sheets
Gmail to RetailedGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to RetailedGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Hero Parser and Retailed, answered
What can start an automation from Hero Parser?
Any of Hero Parser's 2 triggers in the catalog, including New Candidate and New Recruitment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Retailed when something happens in Hero Parser?
Any of Retailed's 9 actions, including Find Goat products, Find prices in database, Find products in database and Find StockX products. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Retailed to Hero Parser?
Retailed has no triggers in the catalog today, so automations start in Hero Parser. If you need the other direction, ask: your agent reads Retailed's API documentation and adds it.
Do I have to build a connector for Hero Parser or Retailed?
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.