Integration
Connect Storydoc to Softwium
When New Version fires in Storydoc, your agent runs Add book in Softwium. 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 Storydoc and Softwium 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 Storydoc can start in Softwium
When New Version in Storydoc
then Add book in Softwium
When New Version in Storydoc
then Add currency in Softwium
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 Storydoc and Softwium
Triggers and actions 1 trigger · 31 actions
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.
Action
Add bookcreates a new fake book, returns HTTP 201. Note: the vendor does not actually persist writes (test/mock API).
Action
Add currencycreates a new fake currency, returns HTTP 201. Note: the vendor does not actually persist writes (test/mock API).
Action
Add peoplecreates a new fake person record, returns HTTP 201. Note: the vendor does not actually persist writes (test/mock API).
Action
Add pokemoncreates a new fake pokemon, returns HTTP 201. Note: the vendor does not actually persist writes (test/mock API).
Action
Delete bookdeletes the fake book with the given ID. Note: the vendor does not actually persist writes (test/mock API).
Action
Delete currencydeletes the fake currency with the given ID. Note: the vendor does not actually persist writes (test/mock API).
Action
Delete peopledeletes the fake person record with the given ID. Note: the vendor does not actually persist writes (test/mock API).
Action
Delete pokemondeletes the fake pokemon with the given ID. Note: the vendor does not actually persist writes (test/mock API).
Action
Get bookreturns the fake book with the given ID, or HTTP 404 if not found.
Action
Get currencyreturns the fake currency with the given ID, or HTTP 404 if not found.
Action
Get peoplereturns the fake person record with the given ID, or HTTP 404 if not found.
Action
Get pokemonreturns the fake pokemon with the given ID, or HTTP 404 if not found.
Action
List booksreturns all fake books (optional ?limit=N query param to cap the count). Read-only test data, no auth.
Action
List currenciesreturns all fake currencies (optional ?limit=N query param to cap the count). Read-only test data, no auth.
Action
List peoplesreturns all fake people records (optional ?limit=N query param to cap the count). Read-only test data, no auth.
Action
List pokemonsreturns all fake pokemon records (optional ?limit=N query param to cap the count). Read-only test data, no auth.
Action
Update bookpartially updates the fake book with the given ID. Note: the vendor does not actually persist writes (test/mock API).
Action
Update currencypartially updates the fake currency with the given ID. Note: the vendor does not actually persist writes (test/mock API).
Action
Update peoplepartially updates the fake person record with the given ID. Note: the vendor does not actually persist writes (test/mock API).
Action
Update pokemonpartially updates the fake pokemon with the given ID. Note: the vendor does not actually persist writes (test/mock API).
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 Storydoc
Storydoc to StripeStripe is a payment processing platform for online businesses.
Storydoc to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Storydoc to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Storydoc to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Storydoc to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Storydoc to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into Softwium
HubSpot to SoftwiumHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SoftwiumSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SoftwiumSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SoftwiumGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SoftwiumGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SoftwiumGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Storydoc and Softwium, answered
What can start an automation from Storydoc?
Any of Storydoc's 1 trigger in the catalog, including New Version. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Softwium when something happens in Storydoc?
Any of Softwium's 20 actions, including Update book, Update currency, Update people and Update pokemon. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Softwium to Storydoc?
Softwium has no triggers in the catalog today, so automations start in Storydoc. If you need the other direction, ask: your agent reads Softwium's API documentation and adds it.
Do I have to build a connector for Storydoc or Softwium?
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 Storydoc and Softwium 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.