Actions from chat (workflows)

Sending email and creating calendar events from chat, the scope of the permissions, and checking before you run them.

Some of the work that follows a meeting can be done straight from chat: drafting and sending a follow-up email, posting a message to Slack, and creating an event in Google Calendar. In every case a draft appears on screen, and nothing is sent to the external service until you have reviewed it and told it to go ahead.

Note

This feature is available in the desktop app (macOS / Windows). You need to have connected whichever of Gmail, Slack and Google Calendar you intend to use. Microsoft 365 mail and calendar are not supported at this time.

Always check the content before sending

This feature has AI produce a draft from the meeting record. The wrong recipient, an incorrect date or figure, or content that was not actually agreed in the meeting can all creep in. Sending, posting and creating an event cannot be undone. Read the recipients and the body again before you go ahead. The points to check are collected under “Checklist before sending” in this article.

What you can do

Action Connection required Currently supported
Drafting and sending email Gmail Google accounts only
Drafting and sending a Slack message Slack channels, group DMs, direct messages
Finding free time and creating an event Google Calendar only people within the same Google Workspace domain

Setting up connections

  1. Open the integrations screen

    Settings > Integrations. Connections are added and removed from this screen.

  2. Connect the services you will use

    Connect whichever of Gmail, Slack and Google Calendar you will use. Email and calendar actions need Gmail and Google Calendar; posting messages needs Slack.

  3. Check which account you are connecting

    A connection is tied to your individual account. Email is sent from the account you connected, Slack messages are posted in your name, and events are created in your calendar. Connecting a shared organisational account makes it impossible to tell who did what, so connect a personal account. If you keep work and personal accounts separate, check here which one you are connecting.

Understand what it can access before connecting

Once connected, Pulse operates the external service with your permissions. The mail you can read, the channels you are in and the calendars you can see become the material for producing drafts. It never accesses more than you can — but by the same token, anything you can see may be consulted. You can disconnect at any time from Settings > Integrations. Disconnecting stops new actions running, but messages already sent and events already created are not undone.

How it works

  1. Ask in chat

    Open chat and write what you want done. Be specific about recipients, the channel to post to, attendees, and the times you would prefer. What is consulted depending on which screen you open chat from is covered in Asking your notes questions (chat).

  2. Review the draft

    An editable draft appears in the chat. Check the content and the destination and correct anything that needs it. For an event, you can pick one of the suggested times or change the date, time and duration directly. Times that clash with another event are flagged.

  3. Tell it to go ahead

    If everything is right, choose “Send” or “Create event”. If you discard the draft, nothing is left on the external service. Where “Save as draft” is offered for an email, choosing it saves it to your Gmail drafts without sending.

Drafting and sending email

Tell chat what kind of email you want, to whom, and what to include. The draft is produced from the meetings in the current scope together with relevant context from the connected Gmail account.

Before sending you can edit the recipients, CC, BCC, subject and body. If you have a signature set in Gmail, you can choose whether to include it. Where something needs filling in, a conspicuous placeholder may be inserted. Replace every placeholder with the real content before sending. Email is sent only after you choose “Send”.

Where saving to Gmail drafts and applying labels is offered, you can save as a draft and apply an existing or new label. The first time you use this, Gmail may ask for additional permissions. Saving as a draft does not send anything.

Examples of how to ask:

Draft an email to everyone who attended this meeting, thanking them and
confirming what was decided. Polite form, no more than three lines of
preamble. Separate our actions from what we are asking of them, and put
a deadline on each request.
Turn today's discussion into an internal report email to the department head.
Plain form, conclusion first, background as no more than five bullet points.
From these three sales meetings, write the weekly customer status email.
Use a heading per customer and make the outstanding concerns explicit.

If you make the same kind of request repeatedly, saving the conditions as a recipe saves rewriting them each time. How to build the instructions is in Writing effective recipes.

How this differs from email prepared automatically after a meeting

For some external meetings, a suggested follow-up email is prepared automatically once the meeting ends. That is a separate feature, described in Writing follow-up emails. With actions from chat, you decide when a draft is made and what goes into it.

Messages to Slack

Meeting content can be turned into an internal update, a progress report or a list of next actions and posted to a Slack channel, group DM or direct message. Specify the destination in what you ask chat.

Before posting, both the destination and the message are shown, and both can be edited. Posting happens in the name of the connected Slack account, and only after you have reviewed it. If you specify a destination that includes people outside your company through Slack Connect, a warning is shown before sending.

  • You can post to channels, group DMs and direct messages.
  • Only destinations you can access within the connected Slack workspace are available.
  • Where channel names are similar and more than one could match, write the exact name including #.
  • For a group DM or direct message, name the people.
  • Where suggestions appear, type at least two characters after @ or # and then choose. People you choose are notified, and channels you choose appear as links.

Examples of how to ask:

Post the key points of this meeting to #project-hokuriku. A summary of no
more than three lines, plus the take-aways as bullets with owners.
Post an internal report to #sales-share. Three headings: “What they asked
for”, “Concerns” and “Next actions”. Use companies' full legal names.
Send Tanaka-san a direct message with what was decided today and just the
parts he is responsible for.

Finding free time and creating an event

Chat can consult Google Calendar, check what is already scheduled, and draft a new event. Tell it the attendees, roughly when, and how long.

Before it is created, an editable draft of the event is shown. You can check the title, attendees, date and time, description, location and video meeting details. Adjust it by picking one of the suggested times, entering a different time, or moving the event in the calendar view and changing its length. Times that clash with another event are marked, so you can see what the clash is before proceeding. Choose “Create event” and it is added to the connected Google Calendar, with attendees notified by Google Calendar.

Where not everyone is free, you are shown the best available options and whose schedule clashes. No event is created until you pick a time and review the draft.

Examples of how to ask:

Set up a 30-minute meeting next week with me and the owners of this
meeting's take-aways. Afternoons preferred.
Set up a one-hour working session with Sato-san and Suzuki-san on Tuesday
afternoon next week. Title it “XX project — specification review”.
Check whether a review meeting for this project is already scheduled.
If not, find options this week and draft one.

What information is consulted

The following is consulted in order to carry out an action.

  • the notes and transcripts of the meetings in the selected scope
  • relevant Gmail context, when drafting email
  • the Slack information needed to identify the destination
  • the calendar information needed to check availability and avoid clashes

All of it within the permissions of the person who connected. Chat history is visible only to you, as explained in Asking your notes questions (chat), and drafts for external actions are likewise invisible to anyone else until actually sent. For data handling generally, see Security and privacy FAQs.

About sending personal data to external services

The email and messages sent by this feature will normally contain personal data — attendees' names, what they said, the names of contacts at client companies. The destination services (Gmail, Slack, Google Calendar) are not processors to whom UNCHAIN, Inc. has delegated the handling of personal data; they are separate providers contracted by you or your organisation. The flow of data created by these actions therefore has to be accounted for on your side, separately from how it is handled inside Pulse.

Before sending a note containing personal data outside, please check it against your company's personal data handling rules and whether it falls within the purposes of use you have specified. Take particular care where the recipients include people outside your company.

LegislationAct on the Protection of Personal Information, Article 27(1) (restriction on provision to third parties)

This provides that personal data must not, as a rule, be provided to a third party without the individual's prior consent. Paragraph 5 of the same Article treats provision accompanying delegation within the scope necessary to achieve the purpose of use as not constituting “provision to a third party”. For actions that send messages or events from chat to an external service, lawfulness has to be secured by the business handling the personal information that performs the action — in most cases the user's employer.

Points to watch when sending email outside your company are in Writing follow-up emails, and how to think about sharing scope is in Sharing controls.

Checklist before sending

Drafts are produced on the assumption that you will review and correct them.

Check
  • the recipients, destination channel and attendee list are as you intended
  • no unreplaced placeholders remain
  • the destination does not include anyone outside your company
  • names, company names, dates, times, time zones and durations are correct
  • nothing that was not actually agreed in the meeting is written as settled
  • owners and deadlines match what was agreed in the meeting
  • links, attachments, location and video meeting details are correct
  • no internal abbreviations or internal nicknames remain in text going outside
  • the tone and level of formality suit the recipient

If anything is wrong, edit the draft directly or tell chat what to change.

If something is not working

Q. No draft appears, or it says it could not be created

A. Check the desktop app is on the latest version and that the action is enabled for your account. Then check under Settings > Integrations that the service you need is connected. How you phrase the request matters too: rather than “what should I say?”, be explicit about the action — “draft an email to X”. If it says processing was interrupted, ask again in the same chat. That happens if generation was stopped partway, another message was sent while the draft was being produced, the connection dropped, or the app was quit before it finished.

Q. It says a connection is required

A. Follow the prompt shown in chat, or connect Gmail, Slack or Google Calendar from Settings > Integrations. Once connected, go back to the same chat and ask again.

Q. The Slack destination cannot be found

A. For a channel, give the exact name including #. For a group DM or direct message, name the people. Also check that the destination is inside the connected Slack workspace and that you have access to it.

Q. An event cannot be created

A. Check that Google Calendar is connected, that permission to create events has been granted, and that a writable calendar is selected. If you have changed permission settings, disconnecting and reconnecting sometimes resolves it.

Q. Can anything be sent without confirmation?

A. No. This feature always includes a review step. Sending email, posting to Slack and creating an event happen only after you have reviewed the draft and told it to go ahead.

Q. Can I use it with Microsoft 365 mail and calendar?

A. Not at this time. Email and calendar actions require Gmail and Google Calendar to be connected.

Related articles

← Choosing an AI modelWriting effective recipes →