Troubleshooting

My flow is not triggering

First, check that the flow is activated — the toggle at the top of the flow editor should be blue. Next, verify the target database is correct by opening the trigger configuration and confirming the database name. For polling-based triggers (Row Added, Row Updated, Property Changed), events can take up to 60 seconds to detect. Check the Logs tab in the dashboard for error entries — if the flow triggered but failed, the error message will tell you why.

If nothing appears in the logs at all, the trigger configuration may not match any events. Try running the flow manually with Run Now to confirm the actions work independently of the trigger.

I see “rate limited” errors

The Notion API allows approximately 3 requests per second per integration. Notumation queues requests automatically to stay within this limit, but flows with many steps (especially inside loops) can still exceed it during bursts.

To fix this, add a Delay step (1-2 minutes) between heavy actions, reduce the number of steps inside loops, or split large flows into smaller ones that trigger sequentially. The rate limit resets every second, so brief pauses are usually enough.

Template variable shows as raw text

If you see {{trigger.Name}} as literal text instead of a resolved value, check these things:

1. Spelling and case — variable names are case-sensitive. {{trigger.name}} is not the same as {{trigger.Name}}. The property name must match exactly as it appears in Notion.
2. Step order — the step that creates a variable must run before the step that uses it. If you reference {{project.Name}} but the query step that saves project is below the current step, it will not resolve.
3. Save result as — confirm the producing step has its “Save result as” field filled in, and the name matches what you typed in the template variable.

Webhook not receiving data

Verify the webhook URL is correct by copying it again from the trigger configuration panel. POST webhooks expect a Content-Type: application/json header — without it, the body will not be parsed into {{trigger.body}} fields. GET webhooks do not carry a request body, so {{trigger.body}} will always be empty for GET requests.

Also confirm the flow is activated. An inactive flow ignores incoming webhook requests entirely.

JavaScript code does not work

The Run JavaScript sandbox has no network access and no filesystem access. You cannot use fetch, require, or import. Only standard JavaScript built-ins (Math, Date, JSON, String, Array, Object) are available.

Check the execution trace for console output — any console.log statements appear there. Make sure your code uses return to pass data to the next step. If you see a syntax error, paste your code into a browser console first to verify it runs.

I hit the execution limit

Each plan has a monthly execution limit. The free tier allows 100 executions per month. Each flow run counts as one execution, but loop iterations count as individual step executions toward the per-run limit of 200.

Check your current usage in Settings > Usage. If you are near the limit, consider optimizing flows to reduce unnecessary runs (e.g., add conditions to triggers, reduce loop iterations). Upgrade your plan for higher limits.

Flow takes too long

Each step has a default timeout of 30 seconds. If an HTTP Request or JavaScript step exceeds this, it fails with a timeout error. For slow external APIs, increase the timeout in the step configuration (up to 120 seconds on paid plans).

If the entire flow is slow, check individual step durations in the execution log. Common causes: large query results (reduce with filters), many loop iterations (reduce max iterations), slow external APIs (add retry logic or increase timeout).

Properties are not updating

Ensure the property name in your Update Page step matches the Notion property name exactly, including capitalization and spaces. “Status” is not the same as “status” or “Status ”.

Also verify the value type matches the property type. Sending text to a Number property, a string to a Date property, or a plain name to a Relation property will fail. Check the error message in the execution log — Notion’s API returns specific type mismatch errors that tell you exactly what went wrong.