Modules: Connect Sheets, AI, Payments and More

Guide

1. 1

   What a module adds

   A module brings three things:

   • Actions — the steps you drop into an Action block. Google Sheets adds Insert Row, Update Row and Delete Row.
   • Triggers — some modules also add new ways for a flow to start. Stripe adds a payment-events webhook; Telegram adds channel posts and membership changes.
   • Credentials — the module knows what it needs from you (a Google account, an API key) and asks for it once, in one place, instead of in every action.

   A module is installed into a whole application — the one selected in the switcher at the top left — not into a single flow.

2. 2

   Open the Modules page

   Click Modules in the left menu. There are two tabs:

   • Installed — what this application already has. The count sits next to the tab name.
   • Marketplace — everything you can add.

   The Marketplace tab hides modules you already installed. Flip the Show installed switch on the right to see the full list. The search box above the tabs matches module names and the names of the actions inside them, so typing row finds Google Sheets even when you cannot remember what the module is called.

   Every card is laid out the same way: logo and name, the module id with its version (google-sheets@1.0.0), a short description, and two counters for actions and triggers. Click a counter to read the full list of what you get before you install anything.

   

3. 3

   Install a module

   Click Install on the card. That is the whole step: the module's actions are created in your application straight away and the card moves to the Installed tab.

   Two badges tell you what happens next:

   • OAuth required — the module needs a connected account (Google Sheets, Gmail, Google Calendar, Notion).
   • API key required — the module needs a key you paste in yourself (OpenAI, Stripe, YooKassa, TomoAds).

   No badge means there is nothing to set up. The Telegram module works through the bot you already connected, and the image and video modules run on FlowCastle's built-in AI providers, so there is no key to paste.

4. 4

   Finish the setup

   If the module needs keys, the setup window opens the moment the install finishes — Set up TomoAds, for example. Each field carries its own How to get it link, pointing straight at the page in the other service where that value lives, plus a one-line hint under the input.

   You do not have to do it right now. Do it later closes the window and leaves the module installed. Fill the fields and press Save keys whenever you are ready.

   

5. 5

   What the Installed tab tells you

   Each card on the Installed tab reports its own state:

   • No badge — ready to use.
   • Setup required (orange) — keys are missing. The card has a Configure keys button that opens the same window.
   • Configured (green) — keys are saved. You can reopen the window and replace a value; leaving a field blank keeps the one you already saved.
   • OAuth required — the card shows a connect-account button, for example Connect Google account. Clicking it opens the provider’s sign-in popup, and afterwards the card shows which account is connected. Notion connects the same way.

   Keys and connections are stored per application, so one Stripe key covers every flow in that workspace.

   

6. 6

   Where module actions show up

   Nowhere new. Go back to the canvas, open an Action block and click Add Action. Under the built-in actions the menu now has a Modules section, grouped by module, each module's actions listed under its logo.

   Pick one and it lands in the block like any other action, with its own fields: a spreadsheet and a row for Insert Row, a chat and a text for Send Message. Everything the Action node guide says about ordering, outputs and variables still applies. Variables go into module fields from the variable picker, where they appear as chips — for example {{lead_email}} in a spreadsheet cell. You never type them by hand.

   The Browse more button at the bottom of the same menu opens the marketplace in a window, so you can install a module without leaving the flow.

   

7. 7

   What is in the catalog today

   Twelve modules:

   • Telegram — group and channel tools: send a message, photo or document, create an invite link, check membership, restrict, ban, promote. Plus two triggers: channel posts and membership changes.
   • Google Sheets — insert, update and delete rows in a connected sheet.
   • Gmail — send mail, and search, read, update or delete messages.
   • Google Calendar — list calendars, create and edit events, check free/busy.
   • Notion — search content, create and update pages, query data sources.
   • OpenAI AI — ask ChatGPT for a text answer, or generate speech audio.
   • Stripe - Payments — checkout sessions, subscription checkout, payment status, refunds, and a payment-events webhook trigger.
   • YooKassa - Payment Provider — the same job for Russian payments, with its own webhook.
   • TomoAds — sponsored messages: a way to earn from your bot instead of charging for it.
   • AI Image Generation — new images from a prompt.
   • AI Video Generation — short clips of 4 to 12 seconds. Rendering takes minutes, so run that action in background mode.
   • Image Processing — predictable edits to images you already have: overlay, crop, resize, convert.

   A guide per module is coming. Until then, the counters on each card list every action it brings, and each action explains its own fields in the editor.

8. 8

   If something did not work

   The Add Action menu has no Modules section. The module is probably installed in a different application. Check the switcher at the top left.

   A module action fails when the bot runs. Open the Installed tab. An orange Setup required badge or a missing account connection is the usual cause: the action fires and the outside service refuses it.

   Uninstall warns that blocks may stop working. It means it. Removing a module deletes its actions, so fix the blocks that use them first.

9. 9

   Next up

   Your bot has all the pieces now — put it in front of real people: Test and Deploy Your Bot