Integration
Connect Amberscript to Ecal
When Job Finished fires in Amberscript, 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 Amberscript and Ecal 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 Amberscript can start in Ecal
When Job Finished in Amberscript
then Add event in Ecal
When Job Finished in Amberscript
then Update 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 Amberscript and Ecal
Triggers and actions 1 trigger · 18 actions
Trigger
Job FinishedTriggers when a job has finished on our platform.
Action
Add glossaryCreate a new glossary of terms that can be referenced by glossaryId on job upload for improved transcription accuracy.
Action
Create New JobThis action creates a new job on the Amberscript platform.
Action
Delete glossaryDelete an existing glossary.
Action
Delete jobDelete a transcription job.
Action
Get jobRetrieve the status/details of a transcription job.
Action
Get job transcriptDownload a finished job's transcript/subtitles in a chosen export format.
Action
List glossariesList all glossaries defined on the account (used to supply glossaryId when uploading a job).
Action
List jobsList all transcription jobs for the account.
Action
Update glossaryUpdate an existing glossary's terms.
Action
Add calendarCreates a new calendar in your ECAL account.
Action
Add eventCreates a new event in an ECAL calendar.
Action
Delete calendarDeletes a calendar along with all of its events and event history.
Action
Delete eventDeletes an event, by its id or reference, from an ECAL calendar.
Action
Get calendarReturns a single ECAL calendar and its full details, looked up by its id or reference.
Action
Get eventReturns a single ECAL event and its full details, looked up by event id or your own event reference.
Action
List calendarsReturns the list of calendars on your ECAL account, optionally including draft calendars.
Action
Update calendarUpdates an existing ECAL calendar's name, categories, reference, genre, note, logo or draft status. Fields left blank are unchanged.
Action
Update eventUpdates 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 Amberscript
Amberscript to OntraportOntraport is an all-in-one CRM, marketing automation, and e-commerce platform.
Amberscript to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Amberscript to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Amberscript to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Amberscript to Google SheetsGoogle Sheets
Amberscript to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
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
Amberscript and Ecal, answered
What can start an automation from Amberscript?
Any of Amberscript's 1 trigger in the catalog, including Job Finished. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ecal when something happens in Amberscript?
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 Amberscript?
Ecal has no triggers in the catalog today, so automations start in Amberscript. 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 Amberscript 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.
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.