Frequently asked questions¶
How do I verify ownership of the Packs redirect URI for Google OAuth verification?¶
To connect to a Google API from a Pack you need to use OAuth2 authentication. Many APIs require scopes that Google deems "sensitive", meaning that Google must approve your integration before other users can sign in. This approval process is known as OAuth verification, and involves many steps and checks.
One of those checks is that Google must verify you own the domain name for all of the domains used by the integration. This includes the redirect URI that users are sent to after they complete the approval screen. For Coda Packs this redirect URL is always:
To meet Google's verification requirements you would need to verify ownership of the
coda.io domain, which isn't possible. While we hope to find a solution to this problem in the long run, at the moment it isn't possible to complete the verification process with Google.
There are some exceptions to Google's verification requirement, for example an app only used internally within a single organization. If you can adjust your Pack to meet one of these exceptions you can work around the problem.
Can you add my company's icon as an option in Coda?¶
Building a template or demo document is an important part of creating a Pack, as it shows users how to apply you Pack to real problems. Many Pack makers wish to use their company's branding on that document for visual consistency.
Coda supports both document- and page-level icons, from a library we source from an external provider. While some this library includes the icons for some popular brands, it's not comprehensive and your brand may not be present. At the moment we don't have a process for adding new icons to the library, nor do we support using custom icons within a document. This is something we hope to address in the future, but for the time being we recommend using a generic icon.