Inside this article
The Coda Pack uses the Coda API allowing you to push/pull data from other Coda docs. To use the Coda Pack, you will need to generate an API key.
To setup your Coda Pack:
- Visit your Coda account page.
- Click on Generate API token, give your token a name, and click Generate API token.
- You can now copy the API token and use it to authenticate your Coda Pack in your doc.
The Discourse Pack uses the Discourse API enabling you to enrich your documents with topics, posts and category information from your customer forums. To use the Discourse Pack, you or your admin will need to generate an API key for you.
To setup your Discourse Pack:
- Visit your Discourse Admin website - this is hosted at https://<your-discourse-hostname>/admin
- Click on the Users tab and click on the user account you wish to associate with an API key
- In the user profile, scroll down to the Permissions section and click on the Generate button to create the API key.
- Use your website https://<your-discourse-hostname>, the API key and the username to configure your Discourse connection.
The FullContact Pack uses the Enrich API, which lets you search FullContact for any additional information on a contact from an email address. You'll need an API key from a FullContact developer account.
To setup your FullContact Pack:
- Visit your FullContact Developer's Dashboard, logging in if necessary.
- Scroll down to the Get Your API Key section and click the "Generate API Key" button.
- Give your API key a name (e.g. "Coda FullContact Pack") and click "Save".
- You should now see your Secret API Key which you can copy onto your clipboard.
The Greenhouse Pack provides seamless integration between your Docs and the Greenhouse Harvest API. To connect your doc to Greenhouse, you'll need to a Greenhouse API Key.
To create your API Key, navigate to the Developer Center:
- Click on the button Create New API Key at the top of the screen
- Give the new key a descriptive name (ex: Coda)
- Select type Harvest as this key will be used with the Harvest API.
- Grant the key the following permissions:
GET: Retrieve Application
GET: List Applications
GET: Retrieve Candidate
GET: List Candidates
POST: Add Candidate
POST: Add Prospect
GET: Retrieve Job
GET: List Jobs
GET: List Users
To create your API Key and Password:
- From your Shopify Admin, go to Apps.
- Click Manage private apps.
- Click Create new private app.
- In the Description section, enter "Coda" for the name of the private app and add your email address as a contact email.
- In the Permissions section, select "Read and Write" access for Customer, Orders, and Products data.
- When you're done, click Save. The API key and password for your Pack connection are displayed on screen.
The Stripe Pack enables you to access your Stripe data directly from within Coda. The Stripe REST API uses API tokens for authentication.
To create your API Key, navigate to your API Key dashboard:
- Locate the key labeled Secret key and click on the Reveal Key Token
- Copy this value and paste it into the Stripe setup dialog
The Twilio Pack provides seamless integration between your Docs and Twilio's SMS API. To connect your document to Twilio, you'll need to create a Twilio account and grab the API key.
To setup your account, you'll need to locate your account SID and auth token. These can be found in the Twilio Console. If you don't have an existing Twilio account, you can signup for a free trial account to try things out.
Once logged in you'll find the credentials at the top of the project dashboard.
Permissions - Who can take actions?
- If you want everyone in the doc to send text messages, select "Anybody". This way not everyone will need to have their own Twilio Account
If you want to install GitHub to manage engineering tasks at your company by:
- Linking to pull requests and having everyone see data about them like author, description, and line counts.
- Not allowing everyone to merge PRs from your doc.
You'll take the following actions in the permissions section of your Pack installation:
- For "Who can view GitHub data using this account?", you should say "Anybody", so everyone in the doc can see the data.
- For "Who can take actions in GitHub using this account?", you should say "Nobody", since you only want the Pack for viewing data.
If you want to use the Gmail pack to allow members of your team to send each other emails from within your doc, you'll choose the following settings:
- For "Who can view Gmail data using this account?", you should say "Nobody".
- Additionally, you probably want every person to authenticate with their own account when sending emails. This ensures that every person can send messages from their own account, and it ensures that nobody can impersonate anybody else.
- For "Who can take actions in Gmail using this account?", you should say "Only you".