Integration
Connect Contacts+ to EOSL
When New Contact fires in Contacts+, your agent runs Find part status in EOSL. 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 Contacts+ and EOSL to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 Contacts+ can start in EOSL
When New Contact in Contacts+
then Find part status in EOSL
When New Tag in Contacts+
then Get part status in EOSL
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 Contacts+ and EOSL
Triggers and actions 6 triggers · 19 actions
Trigger
New ContactTriggers when a contact is created or a business card is transcribed.
Trigger
New Deleted ContactTriggers when a contact is deleted.
Trigger
New Deleted TagTriggers when a tag is deleted from your account.
Trigger
New TagTriggers when a tag is created on your account.
Trigger
New Updated TagTriggers when a tag is updated.
Trigger
Updated ContactTriggers when a contact is updated.
Action
Add Note to ContactAppends a note to a contact.
Action
Create ContactCreates a contact.
Action
Create or Get TagGets or creates a tag.
Action
Delete contactDelete a contact by id.
Action
Delete tagDelete a tag by id.
Action
Find CompanyFind a company by domain or email.
Action
Find ContactFind a contact by name, company, email, phone or any combination.
Action
Find PersonFind a person by email, phone or Twitter handle.
Action
Get contactRetrieve a single contact by id.
Action
Get TagFetches a private or team tag by ID.
Action
List Webhook TriggersLists the webhook event types available to subscribe to.
Action
Remove Tag From ContactRemoves Tags from a contact.
Action
Tag ContactTags a contact.
Action
Update ContactUpdates a contact.
Action
Update tagEdit a tag (rename).
Action
Find part statusLook up end-of-support/end-of-life status by part number in the lookup table.
Action
Get part statusGet a one-line end-of-support/end-of-life status for a single part number, suitable for spreadsheet lookups.
Action
Get product familyGet full end-of-support/end-of-life detail for one product family by its slug.
Action
List product familiesList every tracked product family with its end-of-support/end-of-life status.
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 Contacts+
Contacts+ to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Contacts+ to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Contacts+ to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Contacts+ to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Contacts+ to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Contacts+ to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into EOSL
Peerdom to EOSLPeerdom helps teams navigate change with smart org charts that boost collaboration and performance.
HubSpot to EOSLHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to EOSLSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to EOSLSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to EOSLGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to EOSLGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Contacts+ and EOSL, answered
What can start an automation from Contacts+?
Any of Contacts+'s 6 triggers in the catalog, including New Contact, New Deleted Contact, New Deleted Tag and New Tag. Describe the moment in plain language and your agent picks the right one.
What can your agent do in EOSL when something happens in Contacts+?
Any of EOSL's 4 actions, including Find part status, Get part status, Get product family and List product families. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from EOSL to Contacts+?
EOSL has no triggers in the catalog today, so automations start in Contacts+. If you need the other direction, ask: your agent reads EOSL's API documentation and adds it.
Do I have to build a connector for Contacts+ or EOSL?
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.
Can my AI client use Contacts+ and EOSL without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.