Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Mumble
Tally

Connect Mumble and Tally

Explore ready-made Mumble and Tally templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Mumble with Tally and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Tally
Trigger: Watch New Responses
Mumble
Action: Select an action
1. Select a trigger

  • Triggers when a new form response is submitted.

2. Select an action

  • Add a customer to the Black List. Customers on the Black List will not receive any future messages until removed. Cannot be undone via API - must remove the customer from the 'Black List' label using 'Remove Customer From Label'.

  • Adds a customer to label in Mumble.

  • Create a new customer in Mumble, or update an existing one matched by phone. Supports marketing/tracking attribution, optional chatbot assignment, and up to 15 custom fields per account.

  • Create a new label (tag) in your Mumble account. Returns 409 if a label with the same name already exists.

  • Assign a chatbot to a customer (or turn off the chatbot, or switch to Dolores AI).

  • Assign a Customer to an agent in Mumble.

  • Assign a customer to a team in your Mumble account. Useful for routing inbound conversations to a specific group of agents (sales, support, retention, etc.).

  • Create a WhatsApp message template. New templates start as PENDING and require Meta approval (typically minutes to hours). Currently supports the 'custom' template type with text/image/video/document/audio headers, body variables, footer, and up to 10 buttons (Quick Reply, URL, Phone). Catalog, coupon, carousel, and product templates will be added in a future version.

  • Deletes a label from Mumble.

  • Change a customer's conversation status (New, Open, Pending, Resolved, Spam).

  • Get full details of a single customer by phone number, including marketing attribution and custom fields.

  • Check whether you can send free-form text messages to this customer right now. The 24-hour Meta window opens when the customer last messaged you. If false, you must send a Template instead.

  • Make any custom call to the Mumble API. Useful for endpoints not yet exposed as dedicated modules. ⚠ Test in a sandbox scenario before using in production flows.

  • Remove a customer from a label. Use this to un-blacklist customers (after first ensuring policy compliance), un-VIP, etc.

  • Send a file (image, video, audio, document) by uploading it directly. Use with Make modules that output file data — Google Drive, Dropbox, HTTP Download, etc. Conversation must be active.

  • Send an image, video, audio, or document via public URL. Conversation must be active (within the 24h window).

  • Send an approved WhatsApp template message that has no body variables. The conversation does NOT need to be active.

  • Send an approved WhatsApp template that has body variables ({{1}}, {{2}}, etc.). Provide one value per variable, in order.

  • Send a plain text message to a customer. The conversation must be active — the customer must have messaged you in the last 24 hours. If the conversation is closed, send a Template message instead.

  • pdate an existing customer matched by phone. Any field left blank is left unchanged. Supports marketing/tracking attribution and up to 15 custom fields per account.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Mumble and Tally.

Add a Customer To Black List
Add a customer to the Black List. Customers on the Black List will not receive any future messages until removed. Cannot be undone via API - must remove the customer from the 'Black List' label using 'Remove Customer From Label'.
Action
Add a Customer To Label
Adds a customer to label in Mumble.
Action
Add a New Customer
Create a new customer in Mumble, or update an existing one matched by phone. Supports marketing/tracking attribution, optional chatbot assignment, and up to 15 custom fields per account.
Action
Add a New Label
Create a new label (tag) in your Mumble account. Returns 409 if a label with the same name already exists.
Action
Assign a Chatbot
Assign a chatbot to a customer (or turn off the chatbot, or switch to Dolores AI).
Action
Assign Customer To Agent
Assign a Customer to an agent in Mumble.
Action
Assign Customer To Team
Assign a customer to a team in your Mumble account. Useful for routing inbound conversations to a specific group of agents (sales, support, retention, etc.).
Action
Create a Template
Create a WhatsApp message template. New templates start as PENDING and require Meta approval (typically minutes to hours). Currently supports the 'custom' template type with text/image/video/document/audio headers, body variables, footer, and up to 10 buttons (Quick Reply, URL, Phone). Catalog, coupon, carousel, and product templates will be added in a future version.
Action
Delete a Label
Deletes a label from Mumble.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.