Integration with Albato

What the Albato integration is and why you need it

Albato is a connector service that links BotMan with hundreds of other services (CRMs, Google Sheets, messengers, payment and ad systems) without any coding. The integration works both ways:

• from BotMan to other services — bot events (new subscriber, incoming message, tag added) automatically trigger automations in Albato;
• from other services to BotMan — an event in any service can send a message, add a tag, run a scenario, and so on.

You can:

• pass new subscribers and leads to a CRM or Google Sheets;
• trigger a bot scenario on a payment or event in an external service;
• sync subscriber tags, fields, and statuses;
• collect notifications and analytics in one place.

The integration is especially useful for:

• managing a client base, leads, and orders;
• end-to-end “bot ↔ CRM ↔ spreadsheets” automation;
• passing payments and conversions to external systems;
• working without a developer.

How to connect Albato: step-by-step

The connection is based on a BotMan API key: you create a key in your account and enter it in Albato.

Step 1️⃣: Get your API key in BotMan

• Log in to your BotMan account.
• Go to the Integrations section.
• Click “Connect API” — your personal API key will be created.
• Copy the key.

🔒 The API key grants access to your account data — do not share it with third parties. You can re-issue the key if needed.

Step 2️⃣: Create the BotMan connection in Albato

• In Albato, create a new automation (or open an existing one).
• Choose the BotMan app as a trigger or action.
• On the connection step, click “Add connection”.
• Paste the key from Step 1 into the “API Key” field and save.

Step 3️⃣: Check the connection

If the key is correct, Albato creates the connection without errors. One connection can be reused in any number of automations — you don’t need to re-enter the key.

Triggers: which BotMan events start an automation

• New subscriber — a user subscribed to the bot for the first time.
• Incoming message — a subscriber messaged the bot.
• Subscriber updated — the subscriber’s data changed.
• Tag added — a tag was assigned to the subscriber.

Each trigger passes the event data (subscriber, channel, tag, etc.) to the automation, which you can map into the next steps.

Actions: what you can do in BotMan

• Send message — send a message to the subscriber.
• Find subscriber — get the subscriber’s data.
• Add tag / Remove tag — manage the subscriber’s tags.
• Set system field / Set custom field — write a value to the subscriber’s field.
• Run flow — run a scenario for the subscriber.
• Run broadcast — start a broadcast to your base.

Example automation

Goal: when the “Paid” tag is added, save the subscriber to Google Sheets.

1. Trigger: BotMan → Tag added.
2. (Optional) filter by the needed tag.
3. Action: Google Sheets → Add row, mapping fields from the trigger.

🧠 Good to know

• One connection (one API key) serves any number of automations.
• Triggers fire only on an enabled automation; in test mode they work temporarily.
• Trigger data is available for mapping into all subsequent steps.