Integration
Connect Dynosend to Crossref Metadata Search
When something happens in Dynosend, your agent does the next thing in Crossref Metadata Search. Describe it 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 Dynosend and Crossref Metadata Search 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 Dynosend can start in Crossref Metadata Search
When New Contact in Dynosend
then Find funders by query in Crossref Metadata Search
When New Contact in Dynosend
then Find works by query in Crossref Metadata Search
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 Dynosend and Crossref Metadata Search
Triggers and actions 1 trigger · 18 actions
Trigger
New ContactTriggers when a new contact is added to your audience.
Action
Add tag to contactAdd a tag to a contact.
Action
Blacklist a ContactAdd a contact to the blacklist
Action
Create a ContactAdd a contact to an audience
Action
Delete a ContactDelete a contact from an audience
Action
Get audienceGet an audience by id.
Action
Get ContactGet one contact from an audience by contact_uid (or email)
Action
List audiencesList audiences.
Action
List contactsList contacts.
Action
Send an EventPerform an event for a specific contact
Action
Subscribe contactSubscribe a contact.
Action
Unsubscribe contactUnsubscribe a contact.
Action
Update contactUpdate a contact.
Action
Find funders by querySearch the Crossref Funder Registry for funding organizations matching a free-text query.
Action
Find works by querySearch Crossref's bibliographic metadata for works (articles, books, conference papers, etc.) matching a free-text query, with optional filters and sorting.
Action
Get funderRetrieve metadata for a funding organization and its suborganizations by funder ID.
Action
Get journalRetrieve information about a journal by its ISSN.
Action
Get memberRetrieve metadata for a Crossref member (publisher) by member ID.
Action
Get work by DOIRetrieve full Crossref metadata for a single work given its DOI.
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 Dynosend
Dynosend to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Dynosend to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Dynosend to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Dynosend to Google SheetsGoogle Sheets
Dynosend to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Dynosend to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Crossref Metadata Search
HubSpot to Crossref Metadata SearchHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Crossref Metadata SearchSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Crossref Metadata SearchSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Crossref Metadata SearchGoogle Sheets
Gmail to Crossref Metadata SearchGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Crossref Metadata SearchGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Dynosend and Crossref Metadata Search, answered
What can start an automation from Dynosend?
Any of Dynosend's 1 trigger in the catalog, including New Contact. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Crossref Metadata Search when something happens in Dynosend?
Any of Crossref Metadata Search's 6 actions, including Find funders by query, Find works by query, Get funder and Get journal. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Crossref Metadata Search to Dynosend?
Crossref Metadata Search has no triggers in the catalog today, so automations start in Dynosend. If you need the other direction, ask: your agent reads Crossref Metadata Search's API documentation and adds it.
Do I have to build a connector for Dynosend or Crossref Metadata Search?
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.