How to get help¶
We use a mixture of different platforms to provide support to Pack makers, so review the options below to determine the best way to get help.
For general questions about Packs, or advice on how to build them, we recommend you post in the Coda Community "Making Packs" category. Codans actively monitor the community and answer questions, as well as other Pack makers that have experience with the platform. Posting questions and answers in a public forum helps build up a knowledge base of information that helps everyone.
Search existing questions Post a new question
For a deeper discussion about the specific challenges you are dealing with, we recommend booking a slot during the Packs Office Hours. You'll get one-on-one time with a Coda Developer Advocate to explore new Pack ideas, talk through an issue, or share your screen and do some live debugging.
Problems or bugs¶
If you are experiencing a problem with your Pack or have identified a bug you can reach out to the Coda Support team. Send an email to firstname.lastname@example.org, and include the following information:
- The URL of your Pack in the Pack Studio.
- The URL of a doc where the error occurred (make sure to share it with support).
- Any relevant error messages or snippets of code.
Approvals and exemptions¶
Certain Pack features are restricted by default and require approval before you can use them. Coda enforces these restrictions when you attempt to create a new version of your Pack. This means you can test your Pack locally using the CLI, but will need to have the approval granted before you can test in a real doc.
The following features require approval:
- Sending fetcher requests to multiple network domains.
OAuth2authentication with an authorization and token URL on different domains.
To request approval please fill out the form linked below. Ensure you are signed in with the same Coda account you are using to develop the Pack. We'll review your request and respond with a decision within a few business days.