Today we are announcing two major updates to Packs:
Packs Tables, a magical new way to pull in data to your docs
New Jira, Shopify and Discourse Packs (how meta)
You can help out by upvoting us on Product Hunt and sharing our content on social. Watch the new Packs intro video and read more about our process below.
We knew Packs were pretty special from the beginning. They always felt like the natural evolution of Coda as an all-in-one doc surface. Packs have allowed our users to make incredible docs, and they have been a vital tool to let our users bring their external data into their Coda docs.
Packs have always relied on pasting in URLs, which was never the easy way that we wanted them to work. Sometimes this was the right workflow, but it didn’t work in all use cases. So we set out to build a tool to make the process of pulling data into docs effortless and seamless. Packs Tables are that tool, and they are live for all users today. Packs Tables automatically pull data from our most popular Packs into a table in your doc, so you can work with that data in all the ways you do already in Coda. Packs Tables are added in the normal packs sidebar within your docs.
Packs Tables have unlocked so many amazing use cases, from running Jira dashboards in Coda, checking on a team’s Github requests, organizing email and calendar in one place, and more. All these experiences feel really magical and push us further towards letting anyone build a doc as powerful as an app. The possibilities with Packs Tables are truly endless, and we are so excited to see what you all build with them.
Additionally, our Jira and Shopify packs with Packs Tables are now live. Jira has long been our most-requested pack for a while. The Shopify pack gives superpowers to businesses everywhere. Both the Jira and Shopify packs feature Packs Tables, so you can run your engineering teams and Shopify storefronts right from your Coda docs.
We can’t wait to see what you all make with Packs Tables and our new Jira and Shopify Packs!
Hey, we’ve been looking at lots of new Packs Tables.
Sheets is a trickier one in exactly how you take some of the spreadsheet structure and have it fit nicely into a Coda table without it being too fragile (for example someone adds a new mini table in the same sheet)
What are the kinds of data you were looking to sync into Coda?
Great to see Jira pack in your offer! I gave it a try and wonder if there is a way to connect to a self-hosted Jira instance? Now when I’m trying to connect I’m being taken to Atlassian cloud.
If this is not yet supported, do you have any plans to make it happen in a near future?
Hi Kacper, we’re not currently planning on supporting Jira self-hosted as the APIs work very differently and don’t support some of what we need to make Packs Tables work in the way we need.
For us, I would just be looking to sync a basic spreadsheet structure from Google sheets from a specific worksheet, and have that data live within a Coda doc for calculations etc.
A fair amount of our users have a workflow similar to this right now. It’s not a perfect workaround, but have you read our blog post on connecting Sheets to Coda using Google Scripts? It’s a small amount of setup, but I think you could get most of the benefit of a Sheets pack via that method.
@Asaf_Dafna that’s correct. It would be a bit of additional work to connect the two, but the basic framework is all covered in that post. I’ll add it to the list to get a more direct post up connecting the two.
Using the JIRA pack, so far it’s pretty good. Are there plans to increase the number of filters available. I would love to be able to filter our Epics and Sub-tasks. So I can show just a list of the “User Stories” that the development team is working on.
We’re looking into options here, some of them are tricky because of the way the Jira API works. You can at least filter those out after the sync in the regular Coda filters.
I was trying to use the regular coda filters. But I can’t seem to filter on things like ISSUETYPE = Epic. Even the JIRA templates seem to have issue with this.
