Inside this article
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.
Note: FullContact has individual accounts as well for managing contacts. The FullContact Pack does not use this account type.
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.
Configure User Setup Permissions in Greenhouse Recruiting
In order to enable the Greenhouse Recruiting / Coda integration, you will need the developer permission Can manage ALL organization’s API Credentials.
Contact a Greenhouse Recruiting user in your organization with Site Admin level permissions with the additional user-specific permission Can edit another user's advanced permissions to apply the API credential management permission to your account. Have the user with Site Admin level permissions edit your user account's permissions by navigating to the Configure icon > Users > Your Name.
The user with Site Admin level permissions should navigate to the User-Specific Permissions panel on your user page and expand the Developer Permissions dropdown menu.
Select Can manage ALL organization’s API Credentials so a check is in the checkbox. When finished, click Save.
Repeat as necessary for any other user that should have access to set up the integration.
Create a Harvest API Key for the Greenhouse Recruiting / Coda Integration
To create a Harvest API key for the integration, click the Configure (gear) icon in the upper right-hand corner, and navigate to Dev Center on the left-hand panel. From the Dev Center page, click API Credential Management.
From the API Credential Management page, click Create New API Key to generate the API key for Coda.
In the Create New Credential dialog box, make the following selections:
API Type: Harvest
Description: Coda Harvest API Key
When finished, click Manage Permissions to generate the Harvest API key and automatically assign it the appropriate permissions required by Coda.
In the subsequent dialog box, click Copy to save your API key to your clipboard. Store the API key in a secure location to provide to Coda in the next step. Click I have stored the API Key once you have copied and saved the key.
Note: You cannot access the full API key again after clicking I have stored the API Key. If you lose your API key and need to access it later, you must create a new API key, provide it to the integration partner, and then revoke access to the original key.
On the subsequent page, confirm the following permissions are assigned to your new API key:
GET: Retrieve Application
GET: List Applications
GET: Retrieve Candidate
GET: List Candidates
POST: Add Candidate
POST: Add Prospect
GET: Retrieve Department
GET: List Departments
GET: Retrieve Office
GET: List Offices
GET: Retrieve Job
GET: List Jobs
GET: List Users
Note: Please be aware granting Coda access to all endpoints allows the partner to access all data in your organization's Greenhouse Recruiting account.
If any of the permissions above are not checked, place a check in the box next to the appropriate permission. Click Save when finished.
Your Harvest API key for the Greenhouse Recruiting / Coda integration is created and configured. Input the Harvest API key in Coda.
The Shopify Pack enables you to access you store's Shopify data directly from within Coda. The Shopify Pack uses the Shopify Admin API using API Access Token keys for authentication.
To create your API Key and Password:
From your Shopify Admin, go to Apps.
Click Manage custom apps.
Click Create new custom app.
In the Description section, enter "Coda" for the name of the custom app and add your email address as a contact email.
In the Permissions section, select "Read and Write" access for Customer, Orders, Products, and Inventory data, as well as "Read" access for Locations data. You may have to click the link that says "Review disabled Admin API permissions" in order to see some of these permissions, particularly those for Inventory and Locations, which are buried amid a long list of other permissions.
When you're done, click Save. The API key and password for your Pack connection are displayed on screen.
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".
If you want to add the Jira pack to your doc and bring in your Jira issues or projects first select:
After installing select Add a new
If you have multiple sites for Jira you'll need to choose the one you want to connect and Accept
You can go through this process again to set up another site
The Lever Pack enables you to access your Lever data directly from within Coda. The Lever API uses API tokens for authentication.
To create an API Key, you must be a Lever Super Admin and your organization must be on a Professional or Enterprise Lever plan.
Navigate to Settings > Integrations
Under the heading Lever API credentials, click the Generate New Key button. For the integration name fill in something like “Coda”.
Copy the new API key
Be sure to grant these permissions by checking the corresponding checkboxes:
Read: Read stage
Read: Read candidate
Read: Read posting
Read: List stages
Click the Done button then confirm that you Got it to save the key.
Running into issues with your Pack? Check out this troubleshooting article.