Skip to main content

Understanding Draft Actions for write operations

Coworker's way of keeping you in the loop for any write operation.

Updated this week

When you ask Coworker to take action on your behalf — sending an email, updating a Salesforce record, creating a Jira ticket, scheduling a meeting — it doesn't act immediately. Instead, it prepares a Draft Action: a preview card showing you exactly what it intends to do, giving you the chance to review, edit, or dismiss the action before anything happens.

Draft Actions apply to both Work chat and Agent executions.


What is a Draft Action?

A Draft Action is a structured preview card that appears whenever Coworker prepares a write operation — anything that would create, update, or send something in a connected tool. The card shows you:

  • Which integration is involved (Gmail, Salesforce, Jira, Slack, Notion, etc.)

  • A plain-language summary of what will happen

  • All relevant fields — recipient, subject, record being updated, ticket details, and so on

  • Action buttons: Execute, Edit, and Dismiss

Nothing is sent or saved until you click Execute. You can edit any field inline before confirming, or dismiss the action entirely if it's not what you wanted.


How Draft Actions work

  1. You send a message asking Coworker to take an action (e.g., "Update the Acme deal stage to Qualified in Salesforce").

  2. Coworker prepares the action and displays a Draft Action card in the chat.

  3. Review the card — check the fields, make any edits needed.

  4. Click Execute to confirm, or Dismiss to cancel.

When a chat produces multiple actions, an Action Log tracks each one with its status: Pending, Executing, Done, or Dismissed. A Execute All option appears when two or more actions are pending at once.


Configuring Draft Action preferences per data source

Different write operations carry different levels of risk. Coworker lets you set a preference per integration so the review step matches how much control you want.

Mode

Behavior

Always Review (Ask me first)

A Draft Action card always appears. You must click Execute before anything happens.

Always Execute (Just do it)

No card shown. The action runs immediately and appears in your Action Log afterward.

The first time Coworker triggers an action for a given integration, it will prompt you to choose your preference before the Execute button becomes active. Your choice is saved per integration.

Managing your preferences

You can view and change your Draft Action preferences at any time by going to Account Settings → Draft Action Preferences. Each connected integration shows its current mode, and you can toggle between Always Review and Always Execute at any time.


Supported integrations

Draft Actions are supported across a wide range of write operations, including:

  • Gmail — draft and send emails

  • Google Calendar — create, update, and delete meetings

  • Google Drive — create and edit Google Docs, Sheets, and Slides

  • Salesforce — create and update contacts, accounts, opportunities, and leads

  • HubSpot — create and update CRM records

  • Asana — create and update projects or tasks

  • Jira — create tickets, add comments, update fields, change statuses

  • Slack — send messages to channels or individuals

  • Notion — create and update pages and databases

  • Confluence — create and update pages, add comments

Did this answer your question?