Integration
Connect Swiftype to Ecal
When New Document fires in Swiftype, your agent runs Add event in Ecal. 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 Swiftype and Ecal 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 Swiftype can start in Ecal
When New Document in Swiftype
then Add event in Ecal
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 Swiftype and Ecal
Triggers and actions 1 trigger · 23 actions
- New Document
Triggers when a new Document is created.
- Add domain
Add a crawler domain to an Engine.
- Add engine
Create a new Engine (index).
- Create Document
Creates a new Document.
- Delete document
Delete a document by document_id from a document type.
- Delete domain
Remove a crawler domain from an Engine.
- Delete engine
Delete an Engine by id.
- Get document
Retrieve a single document by external_id from a document type.
- Get engine
Retrieve a single Engine by id or name.
- List documents
List documents within a document type/engine.
- List domains
List crawler domains configured on an Engine.
- List engines
List all Engines for the account.
- Recrawl domain
Trigger a recrawl of a domain's crawled content.
- Search documents
Perform full-text search over documents within an Engine.
- Update document
Update fields on an existing document.
- Add calendar
Creates a new calendar in your ECAL account.
- Add event
Creates a new event in an ECAL calendar.
- Delete calendar
Deletes a calendar along with all of its events and event history.
- Delete event
Deletes an event, by its id or reference, from an ECAL calendar.
- Get calendar
Returns a single ECAL calendar and its full details, looked up by its id or reference.
- Get event
Returns a single ECAL event and its full details, looked up by event id or your own event reference.
- List calendars
Returns the list of calendars on your ECAL account, optionally including draft calendars.
- Update calendar
Updates an existing ECAL calendar's name, categories, reference, genre, note, logo or draft status. Fields left blank are unchanged.
- Update event
Updates an existing ECAL event, identified by its id or your own reference. Only the fields you fill in are changed.
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 Swiftype
Swiftype to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Swiftype to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Swiftype to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Swiftype to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Swiftype to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Swiftype to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into Ecal
Google Sheets to EcalGoogle Sheets
HubSpot to EcalHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to EcalSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to EcalSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Gmail to EcalGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to EcalGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Swiftype and Ecal, answered
What can start an automation from Swiftype?
Any of Swiftype's 1 trigger in the catalog, including New Document. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ecal when something happens in Swiftype?
Any of Ecal's 9 actions, including Update calendar, Update event, Add calendar and Add event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ecal to Swiftype?
Ecal has no triggers in the catalog today, so automations start in Swiftype. If you need the other direction, ask: your agent reads Ecal's API documentation and adds it.
Do I have to build a connector for Swiftype or Ecal?
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 Swiftype and Ecal 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.