How to Integrate Retool with Chanty

To send messages from Retool to Chanty, you first need to create an incoming webhook integration in Chanty. In Chanty, click on the three-dot menu next to the channel you want to receive notifications, select Integrations (or navigate via Settings → Integrations in your Chanty workspace). Look for Incoming Webhooks in the available integrations list. If Chanty's incoming webhooks are available in your plan (typically Business plan), click Add Webhook. Give the webhook a descriptive name like 'Retool Alerts' and select the channel where messages should be posted. After saving, Chanty generates a unique webhook URL — it looks like https://api.chanty.com/webhooks/incoming/[unique-token] or a similar format. Copy the webhook URL. This URL is the endpoint that Retool will POST to — each POST with a JSON body containing a 'text' field sends a message to the designated Chanty channel. Note: If Chanty doesn't show incoming webhooks in your plan or interface, check if Chanty has updated their integration options — Chanty's API capabilities have evolved over time. As an alternative, Chanty also supports Zapier and other automation platforms that can bridge Retool actions to Chanty via their webhooks.

In Retool, navigate to the Resources tab and click Add Resource. Select REST API. Since Chanty webhook URLs are complete endpoint URLs (not base URL + path), set the resource up in one of two ways: Option A (simple): Set the Base URL to the full webhook URL provided by Chanty (e.g., https://api.chanty.com/webhooks/incoming/your-token). Leave the path empty in queries that use this resource. This approach works well if you're only posting to one Chanty channel. Option B (flexible): Set the Base URL to https://api.chanty.com and use the webhook path (e.g., /webhooks/incoming/your-token) in each query. Store different webhook paths as Retool configuration variables if you're posting to multiple channels. No authentication headers are needed — Chanty webhook URLs are pre-authenticated via the unique token in the URL. Add a Content-Type header: Key: Content-Type, Value: application/json. Click Create Resource. To test, create a query with method POST and path set to your webhook path (or leave empty if you used Option A). Set the body type to JSON and enter: {"text": "Test message from Retool"}. Run the query — if 'Test message from Retool' appears in your Chanty channel, the integration is working.

Chanty's incoming webhook payload accepts a JSON body with a text field for the message content. Chanty supports basic Markdown formatting in webhook messages — bold text with **text**, italic with _text_, and links with [link text](URL). Create a sendChantyAlert query with method POST and the webhook path. Set the body type to JSON and compose the message using Retool's dynamic {{ }} expressions to include contextual data. For an order notification, the message body might include the order ID, customer name, amount, and a link to the Retool detail view. Structure the text to be scannable in Chanty's mobile and desktop apps — use line breaks (\n) to separate sections and bold key information. For different event types, create separate queries (sendChantyAlert, sendChantyDigest, sendChantyDeployment) with tailored message formats for each channel. Set all notification queries to manual trigger only — wire them to button event handlers (On Click → Run Query) or to other query event handlers (On Success of an action query → Run notification query). For approval workflows, the notification can include the approval result: 'Order #{{ orderTable.selectedRow.data.id }} has been APPROVED by {{ retoolContext.currentUser.email }}' — making the notification a complete record of who took which action.

1// Chanty webhook message body
2{
3  "text": "**New Order Alert** 🛒\n\n**Order ID:** #{{ orderTable.selectedRow.data.id }}\n**Customer:** {{ orderTable.selectedRow.data.customer_name }}\n**Amount:** ${{ orderTable.selectedRow.data.total.toFixed(2) }}\n**Status:** {{ orderTable.selectedRow.data.status }}\n\n[View in Retool]({{ retoolContext.pageUrl }})"
4}

For automated (non-user-triggered) Chanty notifications, use Retool Workflows — the server-side automation system with scheduled and webhook triggers. Navigate to Retool Workflows in your Retool account and click New Workflow. Give it a name like 'Daily Digest to Chanty' or 'Inventory Alert'. Add a Schedule Trigger block and configure it to run at your desired time (e.g., every weekday at 9:00 AM using cron syntax: 0 9 * * 1-5). Add a Resource Query block connected to your database or external API. Write the query that fetches the data you want to include in the digest (yesterday's metrics, current alerts, etc.). Add a JavaScript Code block to format the query results into a readable message string. Build the message text with newlines and key-value pairs that will read well in Chanty. Add a final Resource Query block pointing to your Chanty REST API Resource. Set method to POST and body to the formatted message object: {"text": {{ codeBlock.data.message }}}. Click Publish to activate the workflow. Test by manually triggering it from the Workflow editor. Monitor run history in the Workflow's execution log to verify messages are delivered on schedule.

1// JavaScript block in Retool Workflow to format digest message
2const metrics = databaseQuery.data;
3const today = new Date().toLocaleDateString('en-US', { weekday: 'long', month: 'long', day: 'numeric' });
4
5const totalOrders = metrics.reduce((sum, row) => sum + row.order_count, 0);
6const totalRevenue = metrics.reduce((sum, row) => sum + row.revenue, 0);
7const openTickets = metrics[0]?.open_tickets || 0;
8
9const message = `**Daily Digest — ${today}**\n\n` +
10  `📦 Orders: ${totalOrders}\n` +
11  `💰 Revenue: $${totalRevenue.toFixed(2)}\n` +
12  `🎫 Open Support Tickets: ${openTickets}\n\n` +
13  `_Sent by Retool_`;
14
15return { message };

The most practical use of the Chanty integration is adding notification side-effects to actions that already exist in your Retool apps. Anytime a user performs a significant action — approving a purchase order, closing a support ticket, completing a QA check — a Chanty notification can inform the relevant team channel. For each important action button in your existing Retool apps, add a sendChantyAlert query to the button's event handler chain. In the button's On Click event handler: 1. Run the primary action query (e.g., updateOrderStatus) 2. On success of the primary query, run sendChantyAlert 3. On success of sendChantyAlert, show a success notification in the Retool UI This chaining pattern (primary action → notification → UI feedback) ensures Chanty is only notified when the action actually succeeds. Avoid sending Chanty alerts before the primary action completes — a notification about an action that then fails is worse than no notification. For high-volume events where not every occurrence warrants a Chanty message, add a condition: only send the notification when a threshold is met (e.g., only alert for orders over $1,000, only notify on ticket escalation to Critical, only alert when error count exceeds 10 in a 5-minute window).

1// Conditional Chanty notification body
2// Only send if order value exceeds threshold
3{
4  "text": "{{ parseFloat(table_orders.selectedRow.data.total) >= 1000 ? '🔔 **High-Value Order Alert**\\n\\n**Order:** #' + table_orders.selectedRow.data.id + '\\n**Amount:** $' + table_orders.selectedRow.data.total + '\\n**Customer:** ' + table_orders.selectedRow.data.customer : '' }}"
5}