With the n8n Pack and this Coda Doc, you now have unprecedented control over and visibility into your n8n instance.
n8n is an amazing workflow automation tool that I’ve used a ton over the past year to help automate huge chunks of work for businesses, but I’ve always been frustrated by the limitations of the n8n interface, especially when it comes to finding executions and workflows.
✨ This document is the dashboard I’ve always wanted for my n8n automations and workflows.
It’s built for anyone who uses n8n or is interested in getting started - not just cloud users, but self-hosted users as well. It’s already pretty powerful, but believe it or not, it can easily be extended to add even more features and capabilities!
Let’s get started.
Set Up Your Doc
Copy this doc to your workspace →
Copy this doc
New to Coda? You’ll be asked to create a free account first
If you don’t have one yet, create an n8n account (1 month free trial) →
, where I share my learnings and struggles as I try to grow my own business.
When I learned that n8n had released a public API and that I could finally build Packs in Coda, I knew the time was right for me to build the bridge between these two awesome tools.
I’ve built hundreds of automations in n8n for many different use cases, but I’ve always been frustrated with the dashboard. Imagine having hundreds of different workflows in there...it’s all but impossible to find anything. A particularly difficult but essential task: finding a specific execution based on when it ran or how long it ran for, so that I can dig into the details and debug what went wrong.
Here’s another one: turning off all active workflows in an emergency situation. This would have saved me a ton of pain at my last company. 😅
I also wanted the ability to get a high level overview of my entire instance. How frequently are workflows running? How long are they running for? Are things operating normally or are there weird things going on?
These were all important features that the n8n dashboard couldn’t provide out of the box. So I created this Pack and this Doc to meet my needs. After all, that’s the magic of APIs and no-code tools, isn’t it? ✨
Now, I can control, access, and monitor my n8n workflows better than ever before. And so can you. Enjoy!
Copy this doc
FAQ
Is using the n8n Pack in this dashboard approved and verified by n8n?
Nope, but I’m sure they’re glad that it exists!
There’s a reason that they made the public API available earlier this year. Don’t just take my word for it, this is from their website:
n8n was created to give developers freedom and flexibility. Since n8n is built around 3rd party API access, it makes sense for us to also provide a publicly available API. Now, you can perform most of the actions that are offered by the n8n UI, but from your own script.
How much does it cost to use this n8n dashboard?
To use this dashboard and sync it to your n8n account, you need:
A Pro Coda account: $10/month
n8n for Coda Pack: $4/month
🎁 For the first month after launch, this Pack will be completely free for everybody!
Note for free Coda account users:
In the Beta Trial period of this Pack, you’ll be able to use this dashboard completely free of charge!
You’ll have a 1,000 row limit (isn’t relevant at the moment, see next FAQ)
Can I see all of my executions?
Almost all. You can see up to 250 at the moment, but very soon we will be able to sync up to the latest 10,000 executions. Currently waiting on a bug fix from n8n before we can implement this.
How frequently does the data refresh?
This depends on your Coda plan!
Pro Coda users can automatically sync the data daily
Team Coda users can automatically sync the data hourly
Note for free Coda account users:
Free Coda users can only sync the data manually
The data doesn’t seem right. Is my n8n instance set up correctly?
If you’re having issues with syncing (”syncing failed”), please try connecting your account again
Step 1: Click Settings Icon in the top right → search n8n → click n8n for Coda
Step 2: Click Settings tab → click the 3 dots → click Sign in again
If you’re having issues with your executions not showing up, please double check that