Integration
Connect Invoco to EOSL
When New Call Completed fires in Invoco, 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 Invoco 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 Invoco can start in EOSL
When New Call Completed in Invoco
then Find 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 Invoco and EOSL
Triggers and actions 5 triggers · 12 actions
- New Call Completed
Triggers when a call (inbound or outbound) on your Invoco numbers completes and appears in your call history.
- New Inbound Call Completed
Triggers when an inbound call on your Invoco numbers has finished. Returns the call's ID, start time, caller, called number, duration and cost.
- New inbound SMS
Triggers when a new text message is received on one of your Invoco numbers.
- New Outbound Call Completed
Triggers when an outbound call on your Invoco account has finished.
- New outbound SMS
Triggers when an SMS is sent from one of your Invoco numbers.
- Get call recording
Downloads the mp3 recording of a call. An error occurs if no recording exists for the call.
- Get call transcript
Returns the transcript and AI analysis (score, call type, summary, speakers) of a completed call.
- Get SMS
Returns a single SMS message by its id, including direction, sender, recipient, text, fragment count and cost.
- List billing history
Returns the billing history (payments) for your Invoco account.
- List call history
Returns your Invoco telephone call history, optionally limited to a date range, including caller, called number, duration, cost and direction for each call.
- List numbers
Returns all of your Invoco telephone numbers, with each number's description and where it currently redirects.
- List SMS history
Returns the text messages sent and received on your Invoco account, newest first, optionally narrowed by date range, direction or phone number.
- Send SMS
Sends a text message from one of your Invoco numbers.
- Find part status
Look up end-of-support/end-of-life status by part number in the lookup table.
- Get part status
Get a one-line end-of-support/end-of-life status for a single part number, suitable for spreadsheet lookups.
- Get product family
Get full end-of-support/end-of-life detail for one product family by its slug.
- List product families
List 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 Invoco
Invoco to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Invoco to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Invoco to MailchimpMailchimp marketing automation and email platform.
Invoco to StripeStripe is a payment processing platform for online businesses.
Invoco to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Invoco to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
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.
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
Invoco and EOSL, answered
What can start an automation from Invoco?
Any of Invoco's 5 triggers in the catalog, including New Call Completed, New Inbound Call Completed, New inbound SMS and New Outbound Call Completed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in EOSL when something happens in Invoco?
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 Invoco?
EOSL has no triggers in the catalog today, so automations start in Invoco. 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 Invoco 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 Invoco 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.