Integration
Connect ContentStudio to CORE
When List Campaigns fires in ContentStudio, 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 ContentStudio 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 ContentStudio can start in CORE
When List Campaigns in ContentStudio
then Discover full text links 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 ContentStudio and CORE
Triggers and actions 5 triggers · 19 actions
- List Campaigns
Lists campaigns (folders) in a workspace. Useful for getting campaign IDs to assign to posts.
- List Labels
Lists labels in a workspace. Useful for getting label IDs to assign to posts.
- List Media
Lists media assets in a workspace media library with filtering, search, and sort options.
- List Team Members
Lists team members in a workspace. Useful for getting user IDs for approval workflows.
- List Workspaces
Returns all workspaces you have access to so you can choose where to post.
- Add Campaign
Create a new campaign in a workspace to group posts.
- Add Label
Create a new label for organizing posts.
- Delete Campaign
Delete a campaign.
- Delete Label
Delete a label.
- Delete Workspace
Delete a workspace.
- Update Campaign
Update an existing campaign's details.
- Update Label
Update an existing label's name or color.
- Update Workspace
Update an existing workspace's settings.
- Upload Media
Uploads a media file from URL into the workspace media library.
- Discover full text links
Finds a link to the full text of a research paper from its DOI, searching CORE and other external sources for the best match.
- Find data providers
Searches CORE's data providers (repositories and journals that supply research papers) and returns the matching providers.
- Find outputs
Searches CORE research outputs (papers and other repository records) by title, author, DOI or a field query and returns the matching outputs.
- Find works
Searches CORE works (deduplicated research papers grouped across repositories) and returns the matching works.
- Get data provider
Returns the details of one CORE data provider (repository or journal), looked up by its CORE id or OpenDOAR id.
- Get journal
Returns a single CORE journal, looked up by its CORE identifier or by ISSN.
- Get output
Returns a single research output (paper) from CORE by its CORE ID, including its metadata, authors, abstract and links.
- Get work
Returns a single research work from CORE, including its title, authors, abstract, DOI, download link and full text.
- List outputs of data provider
Returns the research outputs harvested from a CORE data provider, optionally narrowed by a search query.
- Recommend similar outputs
Returns 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 ContentStudio
ContentStudio to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
ContentStudio to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ContentStudio to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
ContentStudio to Google SheetsGoogle Sheets
ContentStudio to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
ContentStudio to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into CORE
Google Calendar to COREGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
ContentStudio and CORE, answered
What can start an automation from ContentStudio?
Any of ContentStudio's 5 triggers in the catalog, including List Campaigns, List Labels, List Media and List Team Members. Describe the moment in plain language and your agent picks the right one.
What can your agent do in CORE when something happens in ContentStudio?
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 ContentStudio?
CORE has no triggers in the catalog today, so automations start in ContentStudio. 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 ContentStudio 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.