Chanty

Open your Chanty workspace in the browser and click your workspace name in the top-left to open the main menu. Navigate to Settings → Integrations → Incoming Webhooks. Click the 'New Webhook' button. Chanty will ask you to select a channel — choose the channel where you want Bubble notifications to appear (for example, #alerts or #ops). Give the webhook a descriptive name such as 'Bubble App Notifications' so your team knows where messages come from. After saving, Chanty displays the webhook URL. It looks something like: `https://api.chanty.com/webhooks/XXXXXXXXXXXXXXXXXXXXXX`. Copy this URL and store it somewhere safe — you will need it in Bubble. This URL contains the authentication token in the path; treat it like a password. Do not paste it into a public document, a Slack message, or anywhere that others can read it.

In your Bubble app editor, click the Plugins tab in the left sidebar. At the top of the Plugins panel, click 'Add plugins'. In the plugin search box, type 'API Connector' and find the official 'API Connector' plugin published by Bubble. Click Install. This plugin is free and adds the ability to make HTTP calls to external APIs from both client-side and server-side Bubble Workflows. After installation, the API Connector appears in your Plugins tab. Click on it to open the configuration panel. You will see a blue 'Add another API' button — click it to start a new API group.

After clicking 'Add another API', give the API group a name such as 'Chanty'. You do not need to add any shared headers — Chanty's webhook URL handles authentication itself. Click 'Add another call' inside the Chanty group. Name this call 'Send Notification'. Set the method to POST. In the URL field, you have two options: **Option A (recommended for security):** Set the URL as a dynamic parameter so the webhook URL is passed in at runtime from a private Bubble field. In the URL field, type a placeholder like `[webhook_url]`, then in the call's Parameters section add a parameter named `webhook_url` and check the 'Private' checkbox. The full URL becomes your API endpoint at runtime. This prevents the URL from ever appearing in the Bubble editor in plain text. **Option B (simpler, acceptable if API Connector is server-only):** Paste the full webhook URL directly into the URL field, then click the small padlock or 'Private' toggle available in some Bubble versions. In either case, ensure this call is used ONLY from Backend Workflows and never from client-side actions. For the request body, set Content-Type to application/json and add the following body template: ```json { "text": "[message]" } ``` Add a parameter named `message` (not private — it will contain the dynamic text you build per event). Chanty also supports basic markdown formatting in the `text` field: `*bold*`, `_italic_`, and triple-backtick code blocks. You can build richer messages like: ```json { "text": "*New Order* 🛒\nCustomer: [customer_name]\nAmount: $[amount]\nPlan: [plan]" } ``` Click 'Initialize call'. Bubble requires a real successful HTTP response to detect the response schema. For Chanty webhooks, a successful response returns HTTP 200 with an empty body or `{"ok":true}`. You will need to temporarily enter the actual webhook URL and a real message text, then click Initialize. After initialization, you can remove or replace the test values with dynamic parameters.

1{
2  "method": "POST",
3  "url": "https://api.chanty.com/webhooks/<private-token-in-url>",
4  "headers": {
5    "Content-Type": "application/json"
6  },
7  "body": {
8    "text": "<dynamic message>"
9  }
10}

Now you need to create the server-side workflow that calls the Chanty API. In Bubble, Backend Workflows run on Bubble's servers and never expose their logic or parameters to the browser. This is essential for keeping your webhook URL private. Go to the Workflow tab in the Bubble editor. At the top of the Workflow panel, click 'Backend Workflows'. If you do not see this option, your app is on the Free plan — you need to upgrade to Starter ($32/month) or higher before continuing. Click 'New API Workflow'. Name it something like `notify_chanty`. This creates a Backend Workflow that can be triggered from other workflows, scheduled events, or API calls. Inside the Backend Workflow, click 'Add an action'. Search for or scroll to 'Plugins → Chanty → Send Notification' (the API Connector call you configured in Step 3). Click it to add the action. In the action's configuration panel, fill in the `message` parameter. This is where you compose the text that will appear in Chanty. You can use Bubble's dynamic data expressions — for example: - If triggered from a user signup workflow: `'New user: ' + Triggering User's name + ' (' + Triggering User's email + ')'` - If triggered from a payment workflow: `'Payment received: $' + Triggering Order's amount + ' from ' + Triggering Order's customer name` For the `webhook_url` parameter (if you used Option A from Step 3), you can store the webhook URL in a Bubble Option Set (Data → Option Sets → Create Option Set 'Config' → add option 'chanty_webhook_url' with a display field containing the URL). Then reference it in the workflow as `Option Set Config's chanty_webhook_url's URL`. This avoids hardcoding the URL anywhere in the workflow editor UI. RapidDev's team has helped many founders set up this pattern cleanly across dozens of Bubble apps — if you want a free scoping call to review your Backend Workflow architecture, visit rapidevelopers.com/contact.

With the Backend Workflow ready, you can now trigger it from any event in your Bubble app. In the Workflow tab, create or edit the workflow that corresponds to the event you want to monitor. **Example 1 — Form submission:** When your contact form is submitted, add an action 'Schedule API Workflow' → select `notify_chanty` → set 'When' to 'Current date/time' (runs immediately) → pass in the form data as parameters. **Example 2 — Database change:** If you use a Data Things workflow (e.g., when a new order is created), add 'Schedule API Workflow' at the end of the workflow chain. **Example 3 — Scheduled check:** Create a separate recurring Backend Workflow (click 'Add a recurring event' in the Backend Workflows panel) → set an interval (e.g., every 15 minutes) → check a condition (e.g., count of failed transactions > 0) → if condition is true, schedule `notify_chanty`. Each time 'Schedule API Workflow' runs, it consumes Workload Units (WU) in Bubble's post-2023 billing model. Keep notification workflows lightweight and avoid calling `notify_chanty` in high-frequency loops — for example, do not trigger it inside a 'Schedule API Workflow on a list' action that iterates over thousands of records. Batch or aggregate the message before calling Chanty once.

If you need to go beyond outbound notifications — for example, listing channels, fetching recent messages, or managing team members — Chanty provides a REST API at `https://api.chanty.com/v1` that uses an API key for authentication. To get your API key, open Chanty → Settings → API Access (the exact location may vary by Chanty version — check Chanty's support documentation if you cannot find it). Copy the API key. In Bubble's API Connector, add a new API group named 'Chanty REST'. Add a shared header: - Key: `Authorization` - Value: `Bearer [api_key]` - Check the 'Private' checkbox on the value Caution: Chanty's REST API documentation is sparse compared to Slack or Flock. Before wiring any REST endpoint into Bubble, test it in a tool like Postman or the Chanty developer console to confirm the endpoint path, request format, and response shape. Some endpoints may return undocumented errors or change without notice. Initialize each call in Bubble with a real successful response before using it in workflows.

1{
2  "method": "GET",
3  "url": "https://api.chanty.com/v1/channels",
4  "headers": {
5    "Authorization": "Bearer <private-api-key>",
6    "Content-Type": "application/json"
7  }
8}