Can I route different severity bugs to separate Notion databases?

Yes, add a Router module after Typeform with filter conditions for each severity level. Route Critical bugs to an urgent database and Low priority to a backlog database.

What happens if Typeform sends the same bug report twice?

Add a filter that searches Notion for existing items with the same response_id. Use Notion's 'Search Objects' module to check for duplicates before creating new database items.

Why do some file attachments appear as broken links in Notion?

Typeform file URLs expire after 90 days. Always set the file handling to 'Copy files' in the Notion module so files are permanently stored in Notion's system.

Can I automatically assign bugs to specific developers based on component?

Yes, add routing logic based on the bug component field. Use a Router module to check component type and set different assignees in the Notion database creation.

Beginner~12 min setupProductivity & FormsVerified April 2026

How to Route Typeform Bug Reports to Notion with Make

Automatically create structured Notion database entries from Typeform bug reports with severity classification and screenshot handling.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Make

Also on:Zapier N8n

Best for

Teams that need structured bug triage with file handling and severity-based routing in Notion.

Not ideal for

Simple form-to-database syncing without conditional logic or file attachments.

Sync type

polling

Use case type

import

Real-World Example

💡

A 25-person SaaS startup uses this to route customer bug reports from their help center Typeform into a Notion bug database. Critical bugs automatically assign to the CTO, while low-priority issues go to junior developers. Before automation, the support team manually copied bug details from Typeform emails into Notion, taking 5+ minutes per report and often losing screenshot attachments.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

$30/mo if billed monthly

Pipedream

$29/mo

Basic plan

Prices shown for annual billing. Based on published pricing as of April 2026.

Estimated ROI

1000

min saved/mo

$583

labor value/mo

Free

no platform cost

Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.

Implementation

Skip the setup

Import this workflow directly into Make

Copy the pre-built Make blueprint and paste it straight into Make. All modules, filters, and field mappings are already configured — you just need to connect your accounts.

Before You Start

Make sure you have everything ready.

Notion database set up with properties for bug title, description, severity, status, and file attachments

Typeform bug report form with file upload capability and severity selection

Admin access to the Notion workspace where bugs will be stored

Make account with available operations on your plan

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Bug Title	`title`	The main bug summary from Typeform's title question
Description	`description`	Detailed bug description and reproduction steps from Typeform long text field
Severity	`severity`	Priority level from Typeform dropdown (Critical/High/Medium/Low)
Reporter Email	`reporter_email`	Email address of the person submitting the bug report
Status	`status`	Bug status set to default 'New' value for triage

2 optional fields▸ show

Screenshots	`attachments`	File uploads from Typeform file upload field, copied to Notion storage
Browser Info	`browser`	Browser and version information from Typeform short text field

Step-by-Step Setup

Scenarios > Create new scenario > Typeform

Create new Make scenario

Start a fresh scenario in Make to connect Typeform responses to your Notion bug database. This will be the foundation for your automated bug triage system.

1Log into Make and click 'Create a new scenario'
2Click the circular '+' button in the center
3Search for 'Typeform' in the app list
4Select 'Watch Responses' as your trigger

✓ What you should see: You should see a Typeform module as the first step with 'Watch Responses' selected as the trigger type.

Typeform module > Connection > Add

Connect your Typeform account

Authenticate Make with your Typeform account to access your bug report forms. Make will store this connection for future scenarios.

1Click 'Add' next to the Connection field
2Click 'Sign in with Typeform' in the popup
3Authorize Make in the Typeform permissions screen
4Return to Make and verify the connection shows as active

✓ What you should see: The connection dropdown should now show your Typeform account name with a green checkmark.

⚠

Common mistake — Don't use a personal Typeform account if this is for team bug reports — create a dedicated workspace account instead.

Make settings

Connection

Choose a connection…Add

click Add

Notion

Authorize Make

popup window

✓

Connected

green checkmark

Typeform module > Form selection

Select your bug report form

Choose the specific Typeform that collects your bug reports. Make will monitor this form for new submissions and trigger the workflow.

1Click the 'Form' dropdown in the Typeform module
2Select your bug report form from the list
3Leave 'Limit' at 10 for initial testing
4Click 'OK' to save the module settings

✓ What you should see: The form name should appear in the dropdown, and the module should show no error indicators.

⚠

Common mistake — If you don't see your form, check that the connected account owns it — shared forms won't appear in this list.

Scenario > Run once > Typeform module

Test the Typeform trigger

Run a test to pull sample data from your form. This lets Make understand the structure of your bug reports for mapping to Notion.

1Click 'Run once' at the bottom of the scenario
2Submit a test bug report through your Typeform
3Wait 30 seconds, then check if the module shows a '1' badge
4Click the Typeform module to inspect the received data

✓ What you should see: You should see JSON data showing your test submission with fields like answers, form_id, and response_id.

⚠

Common mistake — Typeform's webhook can take 60+ seconds to fire on the free plan — don't assume it's broken if data doesn't appear immediately.

Make

▶ Run once

executed

✓

Notion

✓

Typeform

🔔 notification

received

Scenario > Add module > Notion > Create a Database Item

Add Notion module

Insert a Notion module to create database items from the bug reports. This module will receive data from Typeform and structure it for your bug tracking database.

1Click the '+' button after the Typeform module
2Search for 'Notion' and select it
3Choose 'Create a Database Item' as the action
4Click 'Add' to create a new Notion connection

✓ What you should see: A Notion module should appear connected to your Typeform trigger, with 'Create a Database Item' selected.

Notion module > Connection > Create connection

Connect to Notion

Authenticate Make with your Notion workspace to access your bug database. You'll need admin permissions to create database items automatically.

1Click 'Create a connection' in the Notion module
2Click 'Continue with Notion' in the popup
3Select your workspace and grant Make access
4Return to Make and verify the connection appears

✓ What you should see: The connection field should show your Notion workspace name with a green status indicator.

⚠

Common mistake — You must have edit access to the target database — viewer permissions won't work for creating items.

Notion module > Database ID selection

Select bug tracking database

Choose the Notion database where bug reports will be stored. Make will automatically detect the database schema and available properties.

1Click the 'Database ID' dropdown
2Find and select your bug tracking database
3Wait for Make to load the database properties
4Verify you see fields like Title, Status, Priority, etc.

✓ What you should see: The database name should appear in the dropdown, and property fields should populate below for mapping.

⚠

Common mistake — If your database doesn't appear, refresh the page — Make sometimes caches an outdated database list.

Notion module > Properties > Title/Description mapping

Map bug title and description

Connect the Typeform question responses to your Notion database title and description fields. This creates the core bug report content.

1Click in the 'Title' field for your database
2Select the bug title question from the Typeform data
3Click in the 'Description' property field
4Map the bug description or steps to reproduce from Typeform

✓ What you should see: The Title field should show the mapped Typeform question, and Description should reference the detailed bug report text.

Drop this into a Make custom function.

JavaScript — Custom Function{{if(1.severity = "Critical"; "🚨 CRITICAL: " + 1.title; 1.title)}}

▸ Show code

{{if(1.severity = "Critical"; "🚨 CRITICAL: " + 1.title; 1.title)}}

... expand to see full code

{{if(1.severity = "Critical"; "🚨 CRITICAL: " + 1.title; 1.title)}}

Notion fields

Name

Status

Assignee

Due Date

Priority

available as variables:

1.props.Name

1.props.Status

1.props.Assignee

1.props.Due Date

1.props.Priority

Notion module > Properties > Severity mapping

Set up severity classification

Map the severity or priority level from your Typeform to a Notion select property. This enables proper bug triage directly in your database.

1Find your Severity or Priority property in the Notion mapping
2Click the field and select the severity question from Typeform
3Verify the dropdown values match between Typeform and Notion
4Add a default fallback value like 'Medium' if needed

✓ What you should see: The severity field should show the mapped Typeform response, with matching option values between both platforms.

⚠

Common mistake — Severity values must match exactly — 'High' in Typeform won't map to 'Critical' in Notion without a transformer module.

Notion module > Properties > File attachment mapping

Handle screenshot attachments

Configure file uploads from Typeform to appear in your Notion database. This preserves bug screenshots and supporting files for developer review.

1Locate your file upload field in the Notion property list
2Map it to the file attachment question from Typeform
3Set the file handling to 'Copy files' not 'Link only'
4Test with a sample upload to verify the mapping works

✓ What you should see: File attachments from Typeform should appear as embedded files in the Notion database item.

⚠

Common mistake — Typeform file URLs expire after 90 days — always choose 'Copy files' to store them permanently in Notion.

Notion module > Properties > Status/Assignee setup

Set default status and assignee

Configure automatic status assignment and routing for new bug reports. This ensures bugs enter your triage workflow with proper initial states.

1Map the Status property to a fixed value like 'New' or 'Triage'
2Set the Assignee field to your triage team lead
3Add creation timestamp using Make's 'now' function
4Set any other required database properties with defaults

✓ What you should see: New bug reports should automatically appear with 'New' status and assigned to the triage team member.

Scenario > Run once > Activate toggle

Test and activate scenario

Run a complete test with real form data and verify the bug report appears correctly in Notion. Then activate the scenario for live monitoring.

1Click 'Run once' to test the complete workflow
2Submit a test bug report through Typeform
3Check your Notion database for the new item
4Verify all fields mapped correctly, then toggle the scenario to 'ON'

✓ What you should see: A properly formatted bug report should appear in your Notion database with all mapped fields populated correctly.

⚠

Common mistake — Don't activate until you've tested with real data — sample data from Make doesn't always match live Typeform responses.

Scaling Beyond 200+ bug reports/day+ Records

If your volume exceeds 200+ bug reports/day records, apply these adjustments.

Add operation batching

Use Make's aggregator to batch multiple bug reports into single Notion API calls. This reduces operation count and avoids rate limits when processing report floods.

Implement queue management

Set up a Router to handle critical bugs immediately and queue lower-priority reports for batch processing. This prevents P0 bugs from getting stuck behind hundreds of minor reports.

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Set error handling to 'Break' not 'Ignore' to catch failed bug imports

Applies when: Always

Add duplicate prevention filter using Typeform response_id

Applies when: Always

Configure file size limits in Typeform to prevent 5MB+ upload failures

Applies when: Always

Set up email notifications for scenario errors to catch broken webhooks

Applies when: High volume

Add retry logic for Notion rate limit errors (3 requests/second max)

Applies when: High volume

Test with actual bug submissions, not Make's sample data

Applies when: Always

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Make for this workflow

Use Make for this if you need complex bug severity routing or file handling that goes beyond basic form-to-database sync. Make's visual router lets you send critical bugs to different Notion databases or trigger additional actions like Slack alerts. The module-based approach makes it easy to add conditional logic — route P0 bugs to an urgent board, P3 bugs to a backlog. Skip Make if you just need basic form submissions in Notion without routing — Typeform's native Notion integration handles simple cases for free.

Cost

This workflow uses 2 operations per bug report: one Typeform trigger and one Notion database creation. At 100 bug reports per month, that's 200 operations total. Make's free tier covers 1,000 operations, so you're well within limits. The Core plan at $9/month handles 10,000 operations — enough for 5,000 monthly bug reports. Zapier would cost $20/month for the same volume with their Starter plan. N8N self-hosted is free but requires server management time.

Tradeoffs

Zapier has better Typeform webhook reliability — their triggers fire within 15 seconds while Make can take 60+ seconds. N8N offers more advanced JavaScript data transformation if you need complex bug classification logic. But Make wins on file handling — it properly copies Typeform attachments to Notion storage while Zapier often leaves broken file links. Make's visual router also makes bug severity branching much clearer than Zapier's path rules.

Typeform's webhook occasionally sends the same response twice, creating duplicate bug reports in Notion. Add a duplicate filter using response_id to catch this. Notion's API has a 3-request-per-second limit — if you get flooded with bug reports, Make will hit rate limits and queue operations. File uploads larger than 5MB will fail silently in Make's Notion module, so add size validation in your Typeform. The Typeform trigger polls every 15 minutes on Make's free tier, not real-time webhooks.

Ideas for what to build next

→
Add Slack notifications for critical bugs — Create a second scenario that monitors your Notion bug database and sends Slack alerts when P0 bugs are created.
→
Set up bug status update webhooks — Configure Notion to trigger Make scenarios when bug status changes, automatically notifying reporters about resolution progress.
→
Build bug analytics dashboard — Connect your Notion bug database to Google Sheets or Airtable for automated reporting on bug trends and resolution times.