Integration
Connect Geekbot and Storydoc
When New Report fires in Geekbot, your agent runs Find Analytics Events in Storydoc, or New Version in Storydoc to Get current user in Geekbot. 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 Geekbot 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 Geekbot and Storydoc can do together
From Geekbot to Storydoc
When New Report in Geekbot
then Find Analytics Events in Storydoc
When New Report in Geekbot
then Create a New Story Version in Storydoc
From Storydoc to Geekbot
When New Version in Storydoc
then Get current user in Geekbot
When New Version in Storydoc
then Add out-of-office period in Geekbot
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 Geekbot and Storydoc
Triggers and actions 2 triggers · 28 actions
Trigger
New ReportTriggers when a new standup report is submitted in Geekbot.
Action
Add out-of-office periodSchedules an out-of-office period for you or, if you are an admin, for another team member, covering whole days from the start date to the end date.
Action
Add pollCreates a one-shot Geekbot poll that posts a question with answer choices to a channel.
Action
Add standupCreates a new Geekbot standup with its questions, schedule and broadcast channel.
Action
Delete reportDeletes a standup report you authored, removing its broadcast message if one was posted.
Action
Delete standupDeletes a standup and returns the details of the standup that was removed. You must have permission to edit the standup.
Action
Get current userReturns the user who owns the connected API key, along with the team they belong to.
Action
Get pollReturns one poll you created, including its schedule, channel, members and optionally its questions.
Action
Get reportReturns one submitted standup report, including who posted it, when, and the answer to each question.
Action
Get standupReturns one standup by id, including its schedule, members, broadcast settings and optionally its questions.
Action
List out-of-office periodsReturns out-of-office periods for the team members you can view, ordered by start date, optionally narrowed by users, standups or a date window.
Action
List pollsReturns the active and paused polls you created in Geekbot, optionally filtered by state, channel, anonymity or creation date.
Action
List poll votesReturns the vote results for a poll, grouped by broadcast and question. Without a date range it covers only the latest broadcast.
Action
List reportsReturns submitted Geekbot standup reports within a time window, optionally filtered by standup or user.
Action
List standupsReturns the active and paused standups visible to the connected user, with optional filters for state, anonymity, channel and creation date.
Action
List teamsReturns the Geekbot team tied to the connected API key, including its users who take part in at least one standup visible to the connected user.
Action
Start ReportStarts a standup immediately so its report questions go out, either to all of its participants or only to the users or emails you name. Returns the vendor's confirmation that the standup was queued.
Action
Update standupUpdates a standup's name, schedule, questions, channel and participants. Returns the updated standup.
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 Geekbot
Geekbot to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Geekbot to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Geekbot to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Geekbot to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Geekbot to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Geekbot 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
Geekbot and Storydoc, answered
What can start an automation from Geekbot?
Any of Geekbot's 1 trigger in the catalog, including New Report. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Storydoc when something happens in Geekbot?
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 Geekbot?
Yes. When something happens in Storydoc, your agent can act in Geekbot too. This page covers both directions: Storydoc's triggers and Geekbot's actions are listed here as well.
Do I have to build a connector for Geekbot 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 Geekbot 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.