Integration
Connect MiiTel and Storydoc
When New Meeting fires in MiiTel, your agent runs Find Analytics Events in Storydoc, or New Version in Storydoc to Update an existing comment on a phone call leg in MiiTel. 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 MiiTel 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 MiiTel and Storydoc can do together
From MiiTel to Storydoc
When New Meeting in MiiTel
then Find Analytics Events in Storydoc
When New Phone Call in MiiTel
then Create a New Story Version in Storydoc
From Storydoc to MiiTel
When New Version in Storydoc
then Update an existing comment on a phone call leg in MiiTel
When New Version in Storydoc
then Bulk get hold/unhold events in MiiTel
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 MiiTel and Storydoc
Triggers and actions 3 triggers · 49 actions
Trigger
New MeetingTriggers when a new meeting recording is added in MiiTel.
Trigger
New Phone CallTriggers when a new phone call is recorded in MiiTel.
Action
Add tags to a meetingAdd one or more tags to a video meeting record.
Action
Bulk delete multiple meetingsDelete multiple video meeting records in a single request.
Action
Bulk-delete phone call legsDelete multiple call-detail records by id; 204 on success.
Action
Bulk-delete phone callsDelete up to 100 parent phone-call records.
Action
Bulk get hold/unhold eventsFetch hold/unhold events for up to 100 calls in one request ({"holds": [...]}).
Action
Bulk get phone call leg transcriptsFetch transcripts for up to 20 calls in one request ({"phrases": [...]}).
Action
Bulk partially update phone call legsPartially update multiple call-detail records, returning {"call_details": [...]}.
Action
Bulk update tags on multiple meetingsUpdate tags on multiple video meeting records simultaneously.
Action
Count meeting recordings per folderCount accessible meeting recordings for each requested folder.
Action
Create a presigned URL to upload call audioMint a presigned URL for (re-)uploading a call's audio recording.
Action
Delete a phone call leg commentDelete one comment from a call-detail record.
Action
Get a meetingRetrieve one video meeting record, wrapped as {"video": {...}}.
Action
Get a phone callRetrieve one parent phone call and its nested call legs.
Action
Get a phone call legRetrieve one call-detail record, wrapped as {"call_detail": {...}}.
Action
Increment playback count of a phone call legRecord a playback of this phone call leg; returns when it was recorded.
Action
List a meeting's viewersList the users who have played the video — paginated, most recent first.
Action
Record watch time for a phone call legRecord how many seconds of this phone call leg were played.
Action
Remove tags from a meetingRemove one tag from a video meeting record.
Action
Replace all tags on a phone call legReplace all existing tags on a call detail with the provided list.
Action
Retrieve all tags assigned to a meetingRetrieve all tags currently assigned to a video meeting record.
Action
Retrieve all tags assigned to a phone call legRetrieve all tags currently assigned to a call detail record.
Action
Retrieve a meeting recording's phrase summariesRetrieve the summarized transcript phrase groups of a video, by start time.
Action
Retrieve a meeting recording's summariesRetrieve a video's AI-generated and manual summaries, newest first.
Action
Retrieve call quality metrics for a phone call legRetrieve call quality metrics for a specific call detail record.
Action
Retrieve dial start timestamp of a phone call legRetrieve a call detail's dial_starts_at (ISO 8601); 404 if the id is unknown.
Action
Retrieve the comment list of a meeting recordingRetrieve a video detail's comments, wrapped as {"video_comments": [...]}.
Action
Retrieve the comment list of a phone call legRetrieve a call leg's comments, wrapped as {"comments": [...]}.
Action
Retrieve the transcript of a meeting recordingRetrieve a video's transcript, wrapped as {"phrases": [...]}.
Action
Retrieve the transcript of a phone call legRetrieve a call's transcript, one entry per participant track.
Action
Retrieve topics extracted from a meeting recording transcriptRetrieve the list of topics extracted from a video meeting transcript.
Action
Search phone call legsSearchable list of call-detail records, one row per call leg.
Action
Search phone callsSearch parent phone-call records visible to the caller.
Action
Swap analysis participantSwap which participant's data is used as the primary source for call analysis.
Action
Update a meeting recording summaryUpdate the text of an existing summary on a video.
Action
Update a meeting's access permission settingsUpdate the access permission of a video; returns the updated settings.
Action
Update an existing comment on a phone call legReplace the text of one comment on a call-detail record.
Action
Update a transcript phrase of a phone call legCorrect one transcript phrase, returning the stored phrase as {"phrase": {...}}.
Action
Update the after-call-work end time of a phone call legUpdate a call detail's After Call Work end timestamp (ISO 8601); 409 if already finalized.
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 MiiTel
MiiTel to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MiiTel to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
MiiTel to StripeStripe is a payment processing platform for online businesses.
MiiTel to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
MiiTel to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
MiiTel to PipedrivePipedrive is a sales CRM and pipeline management tool.
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
MiiTel and Storydoc, answered
What can start an automation from MiiTel?
Any of MiiTel's 2 triggers in the catalog, including New Meeting and New Phone Call. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Storydoc when something happens in MiiTel?
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 MiiTel?
Yes. When something happens in Storydoc, your agent can act in MiiTel too. This page covers both directions: Storydoc's triggers and MiiTel's actions are listed here as well.
Do I have to build a connector for MiiTel 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 MiiTel 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.