Integration
Connect EFC Aquila and Storydoc
When New Appointment fires in EFC Aquila, your agent runs Find Analytics Events in Storydoc, or New Version in Storydoc to Add Lead in EFC Aquila. 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 EFC Aquila and Storydoc 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 EFC Aquila and Storydoc can do together
From EFC Aquila to Storydoc
When New Appointment in EFC Aquila
then Find Analytics Events in Storydoc
When New Lead in EFC Aquila
then Create a New Story Version in Storydoc
From Storydoc to EFC Aquila
When New Version in Storydoc
then Add Lead in EFC Aquila
When New Version in Storydoc
then Send Email in EFC Aquila
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 EFC Aquila and Storydoc
Triggers and actions 10 triggers · 19 actions
Trigger
Assessment QueryTriggers when a member's assessment standing on a Programme is recorded or re-assessed, optionally limited by grade, progress, attendance, age or group filters.
Trigger
BirthdayTriggers when a member at the Location has a birthday within the chosen window (today by default), once per member per year.
Trigger
Classes AttendedTriggers when a member reaches a lifetime (or this month's) classes-attended count in your chosen range — fires again each time their attendance count changes within it.
Trigger
Did Not ShowTriggers when a member booked onto a class or event today is marked absent (did not show).
Trigger
Expired MemberTriggers when a member's enrolment expires at the Location (members whose status becomes lapsed), newest expiry first.
Trigger
Member QueryTriggers when a member newly appears in a saved roster search at a Location, such as members who become enrolled or fall inactive.
Trigger
New AppointmentTriggers when a new appointment (a 1-on-1 slot with a member) is booked at the Location, scheduled from yesterday through the next year.
Trigger
New LeadTriggers when a new lead (prospective member) is registered at the selected Location.
Trigger
New MemberTriggers when a member enrols at the selected Location (school).
Action
Add LeadCaptures a lead at a Location, merging into an existing matching lead instead of creating a duplicate. Returns the created or matched Member.
Action
Book SessionBooks a member onto one occurrence of a class session, or every occurrence from that date forward. Returns the confirmed booking; if the member is already booked, the existing booking is returned.
Action
Create AppointmentCreates a one-on-one appointment with a member at a location, optionally as a recurring series.
Action
Create NoteAdds a note to a member's record, optionally pinning it to the top of their note feed or raising it to EFC.
Action
Enrol MemberEnrols a member at a location and sets the programmes they are enrolled on, replacing their current programme set. Returns the member's updated enrolment.
Action
Send EmailSends an email from a Location to a recipient, optionally filing it in a member's conversation. Returns the queued message.
Action
Send SMSSends an SMS text message from a Location through its connected SMS provider, optionally filing it in a member's conversation.
Action
Send TemplateEmails a member using one of the Location's library email templates, with merge fields filled in from the member's record. The message is queued for delivery.
Trigger
New VersionTriggers when a new personalized story version is created in your Storydoc account.
Action
Create a New Story VersionCreates a personalized version of a story template for a prospect and returns its share links.
Action
Find Analytics EventsReturns viewer analytics events (opens, clicks, accepts) for your stories within a date range.
Action
Generate StoryGenerates and publishes a new story from a text prompt, optionally branded for a company.
Action
Get AccountReturns your Storydoc organization's ID and name.
Action
Get StoryReturns one story template, including its dynamic variables.
Action
Get Story VariablesReturns the variables and repeatable content groups a story template accepts when creating a version.
Action
Get VersionReturns one personalized story version.
Action
List FoldersReturns the folders in your Storydoc organization.
Action
List StoriesReturns all story templates in your Storydoc account, optionally filtered by status.
Action
List VersionsReturns a page of personalized story versions, filterable by story, folder, sender, title and status.
Action
Update Story VersionUpdates the personalization data of an existing story version, keeping its manual edits.
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 EFC Aquila
EFC Aquila to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
EFC Aquila to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
EFC Aquila to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
EFC Aquila to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
EFC Aquila to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
EFC Aquila to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Storydoc
HubSpot to StorydocHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to StorydocSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to StorydocSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to StorydocGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to StorydocGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to StorydocGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
EFC Aquila and Storydoc, answered
What can start an automation from EFC Aquila?
Any of EFC Aquila's 9 triggers in the catalog, including New Appointment, New Lead, New Member and Assessment Query. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Storydoc when something happens in EFC Aquila?
Any of Storydoc's 11 actions, including Create a New Story Version, Update Story Version, Find Analytics Events and Generate Story. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Storydoc to EFC Aquila?
Yes. When something happens in Storydoc, your agent can act in EFC Aquila too. This page covers both directions: Storydoc's triggers and EFC Aquila's actions are listed here as well.
Do I have to build a connector for EFC Aquila or Storydoc?
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 EFC Aquila and Storydoc 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.