Integration
Connect HelpSpot to CORE
When New Request fires in HelpSpot, your agent runs Discover full text links in CORE. 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 HelpSpot and CORE 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 HelpSpot can start in CORE
When New Request in HelpSpot
then Discover full text links in CORE
When Update in HelpSpot
then Recommend similar outputs in CORE
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 HelpSpot and CORE
Triggers and actions 2 triggers · 14 actions
Trigger
New RequestTriggers when a new request is created.
Trigger
UpdateTriggers when a request is updated.
Action
Create a New RequestCreates a new request. Please note that one of the following is required; first name, last name, user id, email, or phone.
Action
Get requestGet one request by xRequest id.
Action
List categoriesList request categories.
Action
Update an Existing RequestUpdates a request. Please note that xRequest id is required.
Action
Discover full text linksFinds a link to the full text of a research paper from its DOI, searching CORE and other external sources for the best match.
Action
Find data providersSearches CORE's data providers (repositories and journals that supply research papers) and returns the matching providers.
Action
Find outputsSearches CORE research outputs (papers and other repository records) by title, author, DOI or a field query and returns the matching outputs.
Action
Find worksSearches CORE works (deduplicated research papers grouped across repositories) and returns the matching works.
Action
Get data providerReturns the details of one CORE data provider (repository or journal), looked up by its CORE id or OpenDOAR id.
Action
Get journalReturns a single CORE journal, looked up by its CORE identifier or by ISSN.
Action
Get outputReturns a single research output (paper) from CORE by its CORE ID, including its metadata, authors, abstract and links.
Action
Get workReturns a single research work from CORE, including its title, authors, abstract, DOI, download link and full text.
Action
List outputs of data providerReturns the research outputs harvested from a CORE data provider, optionally narrowed by a search query.
Action
Recommend similar outputsReturns research outputs in CORE similar to a given paper, identified by its CORE ID or DOI, or described by its title, abstract, authors or free text.
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 HelpSpot
HelpSpot to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
HelpSpot to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
HelpSpot to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
HelpSpot to MailchimpMailchimp marketing automation and email platform.
HelpSpot to StripeStripe is a payment processing platform for online businesses.
HelpSpot to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into CORE
HubSpot to COREHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to CORESalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to CORESlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to COREGoogle Sheets
Gmail to COREGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to COREGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
HelpSpot and CORE, answered
What can start an automation from HelpSpot?
Any of HelpSpot's 2 triggers in the catalog, including New Request and Update. Describe the moment in plain language and your agent picks the right one.
What can your agent do in CORE when something happens in HelpSpot?
Any of CORE's 10 actions, including Discover full text links, Find data providers, Find outputs and Find works. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from CORE to HelpSpot?
CORE has no triggers in the catalog today, so automations start in HelpSpot. If you need the other direction, ask: your agent reads CORE's API documentation and adds it.
Do I have to build a connector for HelpSpot or CORE?
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.