Inside this article

Accessing Packs in the button menu
Gmail - Send Email or Create Draft
Google Calendar - Quick Add
Google Calendar - Create Event
Slack - Post Message

Packs and buttons are both powerful tools on their own, but by combining them, you can truly make your doc as powerful as an app. 

Accessing Packs in the button menu

In order to add a Pack-specific button, you'll need to install the Pack first. If you need a reminder of the installation process, you can explore this article. Once you install your Packs, you'll see them in your button menu:

Gmail - Send Email or Create Draft

Using the Send Email or Create Draft Gmail buttons allow you to use Coda as a jumping off point for your communications. To set up a Gmail button, use the following settings:

  • Name - Choose a name for your button that you'll use to reference it in your doc
  • Label - What you would like the button to look like (e.g. "Send email to team")
  • Action - Gmail: Send email
  • Account - Which of your emails accounts you would like to use to send the email
  • To - The email address or alias that Coda should send the message to
  • Subject - What the subject line of the email should say
  • Content - You can type a message or even use the = to create a dynamic message. (e.g., =[Table with Updates Name].Filter(Status!=Done))
  • CC, BCC - If there are other addresses to include, add them here. Note, these are optional fields
  • From, Reply To - Here you can update the email addresses that should appear in the From field, and where people can reply to the email

The only difference between the Send Email and Create Draft button is whether or not Coda sends the mail on your behalf. If you choose Create Draft, you'll see it in your Drafts folder where you can further customize or double check your work.

Google Calendar - Quick Add

The Quick Add button allows you to create shortcuts for quick event creation. Like all buttons, you can put the Quick Add button in the canvas or in a table. To set up the button in a canvas:

  • Name - Choose a name for your button that you'll use to reference it in your doc
  • Label - What you would like the button to look like (e.g. "Make time on the calendar")
  • Description - What type of event you would like Coda to add to your calendar (e.g. "1:1 meeting with Lane on Tuesday at 9:00am)

A great use of quick add is in a table of follow ups:

Notice, in the example above we're using =[Today's Followups]  to populate the description field. Here, you can include the type of event you want in the table and then push the button to schedule. You can even create another button to push all of your buttons at once.

Google Calendar - Create Event

You can also create a button for adding new events to your calendar. To set up this type of button, use the following settings:

  • Name - Choose a name for your button that you'll use to reference it in your doc
  • Label - What you would like the button to look like (e.g. "Create new 1:1")
  • Account - Select which of your calendar accounts you'd like to use
  • Start - When the event should begin (Note, if you have start dates in columns of your table you can use the = to pull from your table)
  • Ends - When the event should end (Note, if you have end dates in columns of your table you can use the = to pull from your table)

Slack - Post Message

If your team uses Slack instead of emails, you can set up a Slack button using the following setup:

  • Name - Choose a name for your button that you'll use to reference it in your doc
  • Label - What you would like the button to look like (e.g. "Request update in Slack")
  • Action - Slack: Post Message
  • Account - Select which of your Slack accounts you would like to post from
  • Content - What you would like Coda to post to Slack. Note, you can use = to pull from Tables (e.g. =[Task Table].Filter(Status !=Done) + " needs to be updated!" )
  • Channel - The Slack channel you would like your message to be posted to (make sure to include the #). If you type @ and a person's Slack handle, they will receive a direct message.
Did this answer your question?