Embed a Tally form in monday.com dashboards and items

Pick the place that fits the job

A training company has two forms. The front desk registers walk-ins all day, and trainers file a report after each workshop. One form belongs on a dashboard and the other on every item, and each comes with its own catch.

For the last row, see Embed a Typeform in monday.com. The column setup works the same way in both apps, with tally.so links in the column. This guide covers the first two.

Build a registration desk on a dashboard

The front desk needs the form and the day’s numbers on one screen. On a dashboard, a walk-in’s registration becomes an item, and a chart on the same dashboard shows data from that board.

1. Front desk submits the form
2. Tally receives the response
3. App creates an item
4. Chart shows the new count

Add the form first:

1. Build and publish the form in Tally, with Full name, Email, Ticket type, Dietary needs and a badge photo upload.
2. Open your monday.com dashboard, add a widget and choose Tally Forms Automation from the apps.
3. Paste the form’s ID or link into Tally Form ID or Form URL.
4. Click Save Settings.

Then, on the board behind the dashboard, add this template and pick the same form:

In Data, map Ticket type to a Status column and Full Response to Item Update. Then add a chart widget that counts the board’s items by ticket:

Each registration now lands on the board, with every answer in the new item’s updates and the upload as a link to the file in Tally:

Fit the form to the widget

The widget loads the form from its tally.so/r link, so it looks as it does to anyone who opens that link. That has a few effects:

• Tally’s embed options don’t apply. Dynamic height, Hide form title and Transparent background belong to Tally’s embed code for websites. The app doesn’t use them.
• The form itself sets the look. To change what the front desk sees, change the form in Tally. A long title or cover pushes the first question down, so keep both short for a small widget.
• A tall form scrolls. With Responsive Width on, the form fills the widget and scrolls inside it. Turn it off to set Custom Dimensions, with a Width and Height in PX or %.

Several forms on one dashboard

Each widget has its own settings, so a dashboard can hold a walk-in form and a room change form side by side. Each form needs its own automation, and both can feed the same board, each with its own group.

Not every form needs an item per response. For short notes that belong together, such as shift handovers, post each response to one item:

Show one form on every item

Now the trainer’s report. Each workshop is an item on a Workshops board, and the report form should be one click away on all of them.

1. Open any item on the board.
2. Add a new view to the item and choose Tally Forms Automation from the apps.
3. On the Tally Form Embedder screen, choose One form for all items.
4. Paste the form’s ID or link into Tally Form ID or Form URL. For a link, the app shows the Detected Form ID below the field.
5. Click Save Settings.

The note on this screen means what it says: the form now shows on every item of the board, and you don’t repeat the setup.

Tie each response to its item

Here’s the catch with one shared form. It’s the same form on every item, so nothing in the response says which workshop it came from. Hidden fields can’t carry that: the view loads the form without URL parameters, and the update templates can’t match on hidden fields anyway.

So the person filling it in has to name the item, in a visible question. Give each item a code in a Text column, and ask for that code in the form:

Workshops

November

Workshop	Workshop code	Trainer	Attendance
Acme workshop	W-104	DL Dana Lee	14
Globex workshop	W-105	SO Sam Ortiz

Then add the update template for the same form:

• update item: map Full Response to Item Update, so the report appears on the item. Map the form’s Attendance question to a Numbers column.
• this column: the Workshop code column.
• this question: the question that asks for the code.
• this condition: an option that updates only the first match and doesn’t create a new item.

monday.com compares the whole text of the cell, ignoring capitalization, so w-104 finds W-104 but 104 doesn’t. Keep the codes unique, so a report can’t land on two items.

What an embedded form leaves out

• Campaign data. Anything after the form ID is dropped, including ?ref=newsletter, so embedded responses have empty hidden fields. To track campaigns, use the form’s public link. See Track UTM campaigns from Tally forms.
• Unpublished forms. The embed is the same as your public link. If the link doesn’t open in a browser, it won’t show in monday.com.
• Custom domains. Use the form ID or a tally.so link.

For everything else the app does, read the Tally monday.com integration guide.