How to make Auto Database Diagrams in Coda (a community journey)

Hi team, I am trying to make a pack that generates a diagram of all pages, tables and relationships in a document. (I believe in self documenting software)

Small Question
How can I take a document as a parameter and get a list of all tables. And a detailed list of all columns in that table?

Wider Context
My goal is to create a pack that uses a formula or button to created Entity Relationship Diagram for each of my Docs. (Example of an Entity Relationship Diagrams below)

The actual diagram is not that hard to make using tools like Using the QuickChart GraphViz API | QuickChart wrapped in the Image() function.

The hard part is getting a list of all tables, and a list of all columns. (Ideally using column type or column formulas to determine if there is a relationship)

Closing thoughts

  • Its possible there is an existing tool or simpler way. If so please let me know.
  • Its possible its more complex and I need to get the API involved. Thoughts?

Cheers for your help!


@Rickard_Abraham to the rescue!

Also - you could take in a doc_id or url and then use codas api to extract all the connections - but it would be some heavy work

1 Like

Thanks! Yeah I’ve got this project going :slight_smile:

It’s hitting every single table with the API.

Unfortunately there’s no support for getting the formulas of external formulas and buttons atm, so I’m waiting for an update there before returning to this project

1 Like

Hi @Logan_Krantz - You can get information about the tables and columns in a doc using the Coda REST API:

Packs can make requests to the Coda REST API, and there is a special type of authentication you can use to authenticate with the API:

Hi Team, I am proud to announce that I put on some good music and programmed like a mad man.

You can take a look at my new pack here:

Create synced database diagrams:

A super easy to use formula:

Was it worth my Saturday? Let me know what you think :grinning:


Hello @Logan_Krantz ,

Nice pack - I particularly like the diagrams.

Testing your pack I am running into a few issues:

Does your pack only allow to keep track of the tables/columns of only 1 document

when my docs are larger, I get a time-out error when making a diagram. I don’t know what is happening under the hood, so perhaps this is a limitation we have to live with? Did you try it on larger documents (say, with 75 tables)?

Greetings, Joost

Great Pack @Logan_Krantz! I love the attention to detail on the Pack listing, as well as the featured doc. I could see this being useful for a lot of folks.

@joost_mineur - All regular sync tables have a limit of one table per-doc. You can however add multiple syncs to the table, allowing you to bring in different sets of data:

If for UX reasons it is important to have distinct tables then @Logan_Krantz would have to change the table to by a dynamic sync table instead, like the pattern employed by Cross-doc.


Hi @joost_mineur , Thanks for having a look.

  1. The synced tables can be synced to more then one table at a time. Thank @Eric_Koleda for your quick answer above.

  2. Ill have to take a look in the new year at timeout limitations. My biggest doc only had 20 tables but thanks I’d definitely like to support bugger documents. Would you be opposed to removing the data and sharing me a copy of the doc so I can see the errors you are getting?

Finally, @Eric_Koleda Ill have a read of dynamic sync tables and see if its something I am interested in supporting :smiley:

1 Like

Helo @Logan_Krantz ,

Unfortunately, stripping the data out of my doc is almost impossible, with a 100+ tables, text colums, hidden stuff, etc.

But I will try to cook up something to demo where it goes wrong. I will be a couple of weeks, but I will try to make some time for this.

Greetings, Joost

No problem, it’s a busy time of year. Shoot me a message or post here when you have a sample, and I’ll see what I can do!
Thanks for being my first “stress test“ :joy:

@Logan_Krantz The pack errored out for me as well; we have around 60-70 tables with many hidden columns. Let me know once you’re able to apply a fix - I love the idea behind your pack and know it will help our team understand connection points between tables.

Hey Chris, thanks for having a play.
With 70 tables I assume the GET request is simply exceeding the maximum url length.

I should be able to update it to a POST request without this limitation in the new year.

Can you send me a screenshot of your error message?

@Logan_Krantz Sure, here’s a screenshot:

1 Like

Late to the party!

Love what @Logan_Krantz and @Rickard_Abraham are doing but I wanted to jump in with my own spin!

I just launched a DB Diagram pack that enables you to create an interactive and editable database diagram.

Check out the pack here

Or learn how to use it here


Heck yeah!! looks amazing, love that you can interact with it (you couldn’t do that with which I used)

1 Like

The biggest downfall is that you have to do the manual step of copy/pasting every time you want an UPDATED diagram.

I really wanted dbdiagram to have an API so I could send the code snippet generated by the pack to dbdiagram and have it generate the image for me.

But it doesn’t

If you find any other service that generates db diagrams using DBML (database markup language) and has an API, let me know! We should do a collaborative!


Ah right, still has great potential! has recently gotten an API but it’s not interactive :frowning: :thinking:

1 Like

I am loving the progress we are making in automatic coda diagram!
Thanks Scott! I love the look of DBML as an alternative to the older DotML that I am using.
Souch talent in this thread :grinning:

Thanks Chris for the image. It looks like all the API calls are exceeding the maximum time coda is willing to wait for the pack.

I can to look into Async API calls to speed it up and extending that time limit as well.

1 Like

Haha yeah! The three diagramigos :sunglasses: