Integration

Connect BotMape to EOSL

When something happens in BotMape, your agent does the next thing in EOSL. Describe it in plain language and the automation is built, tested on every branch and kept running.

BotMape1 triggerBotMape8 actionsEOSL4 actions

Browse all apps

Build it

What do you want BotMape and EOSL to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with BotMape and EOSL

Triggers and actions 1 trigger · 12 actions

Trigger
New Lead Captured
Triggers when a new lead is captured — either from a chat conversation or added manually.
Action
Add agent
Create a new AI agent with custom configuration and personality. POST /api/chatbots
Action
Add knowledge base entry
Add training content (FAQ, documentation, policies) to an AI agent; auto-embedded. POST /api/chatbots/:chatbotId/knowledge
Action
Create Lead
Creates a new lead in your CRM. Use this to push leads from other tools into your CRM automatically.
Action
Delete knowledge base entry
Remove a specific knowledge entry from an AI agent's training data. DELETE /api/chatbots/:chatbotId/knowledge/:knowledgeId
Action
Get agent
Retrieve detailed information about a specific AI agent by ID. GET /api/chatbots/:id
Action
List agents
Get all AI agents owned by the authenticated user with their configurations. GET /api/chatbots
Action
List knowledge base entries
Retrieve all knowledge base entries that train an AI agent's responses. GET /api/chatbots/:chatbotId/knowledge
Action
Update agent
Update an existing AI agent's configuration, personality, or appearance. PUT /api/chatbots/:id
Action
Find part status
Look up end-of-support/end-of-life status by part number in the lookup table. Endpoint: GET /data/lookup.json
Action
Get part status
Get a one-line end-of-support/end-of-life status for a single part number, suitable for spreadsheet lookups. Endpoint: GET /cell/{part}.txt
Action
Get product family
Get full end-of-support/end-of-life detail for one product family by its slug. Endpoint: GET /api/v1/family/{slug}.json
Action
List product families
List every tracked product family with its end-of-support/end-of-life status. Endpoint: GET /api/v1/families.json

Each app on its own

The other way round: EOSL to BotMape