Skip to main content
Workflow notifications use the same icon and color as the workflow in the Workflows list.
Before opening Connie Settings: while a new workspace’s first run is unfinished, Settings sends you back to it: answer its two questions, then reopen Settings. Direct Settings links follow the same check. New workspaces use free credits, with no card or trial. Billing (?tab=plans) remains available during setup. See Settings access during setup.
Connie tells you when something needs your attention: an approval is waiting, a workflow failed, a task was assigned to you, an account disconnected, or your credits are running low. You see these on the Notifications page, and, for most events, by email as well. You decide which events reach you, and how, in Settings → Notifications. An Internal workspace’s out-of-credits notice links back to the workspace with Open workspace. It does not offer a subscription; paid work waits until more credits are added. Where:
  • Notifications is the last row of the Workspace group in the left sidebar · https://connie.ai/<workspace-id>/notifications. Its count is red and shows how many notifications wait for you to act (approvals, decisions, accounts to connect and access requests), as the Tasks count does; with nothing to act on, it shows no count. In the collapsed sidebar it is a red dot on the bell icon. Notifications require an account and completed setup.
  • Settings: sidebar → Settings → Notifications · https://connie.ai/<workspace-id>/settings?tab=notifications (or https://connie.ai/settings/notifications, which works without a workspace ID)
Your agents notify you here too, for example when their work needs a decision or an account, when an approval, a question or an account has waited on you for a day (one reminder, once), or when background work posted an update. An approval card raised by a routine or other work nobody is watching is also sent by email and Slack after about five minutes, see Agents’ notifications. A notification that asks you for a decision, an answer or an account clears itself once it is no longer asked, for example when you decided it on its card. See Agents’ notifications. Before signup, Notifications says Create your account to access your workspace. Once you’re signed up, it opens your personal notifications and approvals.

Three kinds of notification

  • In-app: saved on the Notifications page. The count on the Notifications row shows, in red, how many notifications wait for you to act (approvals, decisions, accounts to connect and access requests), up to “99+”. Notifications that only tell you something are not counted.
  • Email: notifications are sent from Connie (noreply@connie.ai). Account authentication emails use support@connie.ai and aren’t controlled by notification preferences. See Emails from Connie for the full list.
  • Pop-ups: short messages at the edge of the screen that confirm something you just did. They disappear on their own and aren’t saved anywhere. They appear in the bottom-right corner; while a side panel or a dialog is open there, they appear just to its left, or above it when there isn’t room beside it, so they never cover its Save or Cancel buttons.

Open your notifications

While notifications load, placeholders match the compact notification cards. Approval required shows placeholders for the approval buttons, Completed shows outcome badges, and All activity shows a mix of row types.
1

Click Notifications

Click Notifications in the Workspace group of the left sidebar. The Notifications page opens: its header, then the All activity, Approval required and Completed tabs with Search notifications…, then the list.
2

Pick a tab

  • All activity — everything.
  • Approval required — decisions waiting on you right now, with a red count.
  • Completed — approvals and access requests that have already been decided. An Agent’s needs a decision or needs an account connected notice also moves here as soon as that exact wait is resolved. Its headline changes to [agent]’s decision request was resolved or [agent]’s connection request was resolved, with a Resolved badge, in both Completed and All activity, including older notifications. Its description says the work is no longer waiting. Work that was stopped instead reads [agent]’s work was stopped, with a Stopped badge, and its description says it was stopped. Resolved does not mean the action was approved or the account was connected. An action Connie asked about in a chat, an Agent or an MCP client stays here for 7 days after it is decided, wherever it was decided (its card in the chat, the Notifications page or the Agent’s page). In a shared chat, it’s listed for the person whose request it was and for the member who decided it. Its row shows Approved, Declined or Couldn’t run, who decided (“By you” when it was you) and what it acted on; hover the badge to see when, for example “Declined by you · Oct 20, 9:25 AM”.
If anything is waiting for you, the page opens on Approval required.
3

Find something

Type in Search notifications…. It matches the start of words in the title, the description or the workflow name, so “fail” finds “failed” but “edit” won’t find “credits”. From three characters, search covers all of your active notifications, including ones older than the newest 50. One- and two-character searches filter the notifications already shown.
4

Open or close

Each notification uses its module’s navigation icon, or the specific Object or tool icon when available. Icon colors and backgrounds match the corresponding module, Object or tool category elsewhere in Connie; a tool’s brand logo sits on a gray background. CSV import notifications use the destination Object’s icon and colors. Connection notifications use provider logos, including Calendly and Google Calendar. Approval notifications also use the icon of their source module: Chat, Agents, Workflows, or Connect for MCP requests. AI chat notifications, including tool approvals, use an outlined speech bubble, in red on a pale pink background. Access requests use a shield icon. Click a notification to go to the thing it’s about. The page refreshes by itself when a new approval or notification arrives.
When the page loads, every notification it shows is marked as read. The count on the Notifications row goes down when what it counts is settled: you decided it, or it is no longer asked. There’s no separate “Mark all as read” button.

Approve or decline on the Notifications page

Approvals that wait on you appear on the Notifications page, on the Approval required tab. These include workflow approval steps, approvals that Connie asks for in Chat or in an Agent, an Agent’s notification that it needs a decision or an account connected, and requests from people who want access to your workspace, a chat or a workflow, or edit access to a List (Request edit access on a public List). Open an Agent wait notification to answer its card, connect the account or skip it where it was asked. Other questions and connect cards that did not send an Agent wait notification remain in their conversation.
1

Open Approval required

Click Notifications in the sidebar, then Approval required.
2

Decide

  • Workflow approvals and access requests: click Approve or Decline. The row then shows Approved or Declined. If the workflow stopped waiting before anyone answered, it shows expired.
  • An access request says under its message what Approve gives: Approve: Join workspace as Member for someone outside the workspace, or, for a member, what they asked to open, such as Approve: View this chat, Approve: View this Workflow or, from a public List link, Approve: Edit this List. When someone outside the workspace asks from a chat’s link, the row names the chat, for example Alex requested access to the chat “Q3 pipeline”, and clicking it opens that chat. Approve still only adds them as a Member; access to the chat is a separate request.
  • An action Connie wants to run in a chat or Agent: click Approve or Decline. Approve runs that one action only. To allow a paid tool for the rest of a chat, or always, answer its card in the chat instead (see Approvals in Chat). If a chat action you approved can’t run as it was saved, or a workflow it deletes was renamed, set live, turned off or deleted after Connie asked, its row shows Couldn’t run instead of Approved; nothing ran, and Connie corrects it and tries again, or asks again, in the chat.
  • What an action costs shows in a green pill: a coin and the number of credits, for example 1. Hover it to read “Running this action will cost 1 credit”. An AI run (an AI Agent or an AI column), like any tool whose cost depends on what it uses, shows Usage based, as its chat card does. Free actions show no pill. A known lookup price stays numeric even if it may find no result. When AI usage is charged on top, the pill keeps the known amount and adds AI usage; hover it for the full charge explanation.
  • Approvals that need context first show Review. Click it to open the chat or Agent and decide there.
  • An action that deletes something says what it deletes, with the same details as its card in the chat, for example “Deal: “Acme renewal” · Created: 15 Jan 2026, 17:00 UTC · Deletes records”. If the page can’t show what it would delete, the row has no Approve and reads “What it would delete isn’t shown here. Open the chat to review it.” Click the row to decide in the chat.
3

Do many at once (optional)

Tick rows using the checkbox on their avatar, then click Approve selected (N) or Decline selected (N) in the page header. With nothing ticked, the header’s Approve all and Decline all answer every waiting approval in the list. If any of them deletes something, Approve all and Approve selected (N) ask first and name what goes, for example “Approve 3 actions?” and “This deletes the deal “Acme renewal”.” An MCP client’s action whose tool can delete or overwrite data asks too, named by what it does, for example ““Delete a record on 3 records” can delete or overwrite data.” Click Approve all to go ahead, or Cancel to send nothing.
More about approvals: Approvals in workflows and Agents and Approvals in Chat.

Delete notifications

  1. Tick the rows you want to remove.
  2. Click Delete in the page header.
Deleting a normal notification just removes it from your list. Deleting a workflow approval is different:
  • Only workspace owners and admins can delete workflow approvals.
  • If the approval is still waiting, Connie asks “Delete an approval that is still waiting?”. Click Delete anyway only if you’re sure: the workflow steps that were waiting for it won’t run.
  • Chat and Agent approvals can’t be deleted. Approve or decline them instead.

Choose what reaches you

1

Open notification settings

Click Settings in the sidebar → Notifications (under Account).
2

Find the event

Scroll to Activity. Each row is one kind of event, with a switch for In-app (the Notifications page) and Email, and a Slack switch on rows Connie also sends to Slack (today Approval tasks). Other rows show a dash in the Slack column.
3

Switch it on or off

Click a switch. It saves right away and a Saved check appears. Turn every switch on a row off to stop hearing about that event at all.
Your choices apply to your account in every workspace you belong to. If this workspace has more than one Slack workspace connected and your Slack account is linked in two or more of them, a Slack section below Activity lets you choose which Slack workspace your Slack notifications go to in this workspace. Without a choice, they go to the Slack workspace whose connection was updated most recently. With one Slack workspace, or none, the section doesn’t show. You can also ask an agent to change them, for one row or for all of them at once (“email only for everything”). Connie changes them in one go, tells you how many it changed, and leaves Payment & subscription issue as it is. Only your own settings change, never a teammate’s.

The Activity list

“Admins only” means the event only goes to workspace owners and admins, even if other members switch it on.
A few rows in the list don’t send anything yet: Schedule paused after failures, Schedule message failures, everything under Pages, Token expiring, and MCP server unreachable. Changing them has no effect today.
Task due says “near to overdue date”, but what you actually get is a Task overdue reminder for each overdue task, once a day (around 09:00 UTC), until you complete or cancel it, move its due date into the future, or it is more than 90 days overdue. The reminder says “was due 1 day ago” for one day and “was due 2 days ago” for two days. The Daily task digest says “at 9AM by default”: it’s sent at 09:00 UTC, not your local time.In workspaces with the Tasks page, Task due tells you once when a task becomes overdue, and again only if its due date changes and that date passes too. The digest names each task by its identifier, for example “LUM-5 Call Acme”.
The three Personal notifications switches at the top of the page (Include message preview, Play notification sounds, Send notifications while I am off) are disabled and marked as unavailable. Saved choices are kept but don’t change anything yet. In particular, the sound for new Inbox messages still plays. To silence it, mute the browser tab.
If personal preferences fail to load, Connie shows “Couldn’t load your personal notification preferences.” with Retry. The Activity table and workflow approval setting remain available.

Email reviewers about approval requests

Under Workflow approvals at the bottom of the page, the switch Email reviewers about approval requests decides whether workflow approval requests are also emailed, not just shown on the Notifications page. It’s off by default and applies to everyone in the workspace. Any member can change it. Each reviewer’s own Approval tasks → Email switch still applies on top of it. This switch covers steps that use Require approval. Workflows built with the older Human Approval step email their approvers whatever this switch says (each approver’s Approval tasks → Email switch still applies).

Manage a teammate’s notifications (owners and admins)

Owners and admins can change another member’s notifications for this workspace, for example to stop someone getting too many emails.
1

Pick the member

In Settings → Notifications, click Editing: You above the Activity list and choose the member. (It only appears when there are other members you can manage. Admins can’t pick owners.)
2

Change their switches

A notice confirms “You are editing notifications for [name]. Changes apply to this workspace only and override their own settings.” Change any switch. Changed rows show Set by owner with a Reset link.
3

Use the shortcuts (optional)

Click Turn off all email to switch off every email for that member at once, or Reset in the notice to undo all your changes and go back to their own choices.
Your changes win over the member’s own choices, but only in this workspace. Payment & subscription issue can’t be changed.

Who gets what

  • Owners and admins only: payment and subscription, credit warnings, new members joining, workflow failures and completions, and calendar disconnections.
  • Approvers: workflow approval requests go to the people chosen as approvers on the step. If anyone may approve, they go to the workspace owners and admins.
  • Just you: tasks assigned to you, your overdue tasks and digest, mentions of you, your role changes, accounts and apps you connected, your AI tasks, and your meetings’ notetaker problems.

@mentions

Type @ and pick a teammate to mention them. What happens next depends on where you wrote it: Mentioning a record, list or date doesn’t notify anyone. Only mentions of people do. To share a comment, open its More options menu → Copy link. The link opens the record with the comment in view. To change one of your own comments, open its More options menu → Edit. It opens in the same box you write comments in, with its text, mentions and images: type @ to mention someone, add or remove images, then press Enter or click Save (Shift+Enter starts a new line, Esc or Cancel keeps the comment as it was). Someone you mention for the first time while editing a comment is notified, as on a new comment; someone the comment already mentioned isn’t notified again.

Good to know

  • Per workspace: the Notifications page shows notifications for the workspace you’re in. Switch workspace to see the others. Waiting approvals count towards the number on the Notifications row.
  • The newest 50: the Notifications page shows your 50 most recent notifications in this workspace, plus every waiting approval.
  • Repeat limits: to avoid floods, Connie sends at most one notification of the same kind about the same thing per hour (or per 30 minutes for less urgent events). Payment and other critical notices are never held back.
  • Repeated workflow failures: while a Workflow run failed notification is unread, more failures of that workflow update it instead of adding new ones. It shows how many times the workflow failed, the latest reason and a link to the latest failed run.
  • Live updates: the count on the Notifications row updates as things happen, and when you come back to the tab.
  • Credits: notifications and emails don’t use credits.
  • Plans: notifications work the same on every plan.
  • Reminders from Chat: a reminder you set in Chat (“remind me Friday at 5pm to call Tesla”) arrives on the Notifications page when it is due and links to the record it is about. Until then, ask the agent to list, change or delete it.

Troubleshooting

Why: the number counts only what waits for you to act: approvals (a chat approval writes no notification), access requests and an agent’s request for a decision or an account. They are listed on Approval required. Fix: open Approval required.
Why: the count shows only what waits for you to act. It goes down once that is settled: you or a teammate decided it, it expired, or its work stopped or finished. Fix: nothing to fix. Decided requests are under Completed, and your notifications are still in All activity.
Why: workflow failure and completion notices go only to workspace owners and admins, not to the person who built or ran the workflow. Completions are only sent for runs of 30 seconds or more, and the completion email is off by default. Fix: ask an owner or admin, or ask to be made an admin. Admins can turn on Workflow completions → Email. A run you start from Connie’s chat is different: whatever your role, that chat posts the run’s outcome when it finishes and you get one notification for it (never two, even as an admin).
Why: billing and credit notices only go to workspace owners and admins. Fix: ask an owner or admin. See Members and roles.
Why: mentions in record comments and field comments only appear on the Notifications page. Fix: check the Notifications page. Mentions in Notes and task comments do send an email.
Why: an edit notifies only the people it mentions for the first time, so nobody hears twice about the same comment. Fix: to remind someone, mention them in a new comment.
Why: mentions in record comments and field comments don’t follow the Mentions switch. Fix: there’s no setting to stop them today. Delete them from the Notifications page.
Why: Task due sends one reminder per overdue task each day, around 09:00 UTC (in workspaces with the Tasks page, once per task and due date). Fix: complete the task or change its due date, or turn off Records → Task due.
Why: it’s off by default, and it’s sent at 09:00 UTC rather than your local time. Fix: turn on Daily task digest and expect it at 09:00 UTC.
Why: Email reviewers about approval requests is off by default, or the reviewer turned off Approval tasks → Email. Fix: turn on the workspace switch under Workflow approvals, and check the reviewer’s own switch.
Why: members can’t delete workflow approvals. Fix: approve or decline it instead, or ask an owner or admin.
Why: approvals from Chat and Agents can’t be deleted by anyone. Fix: click Approve/Allow or Decline.
Why: deleting a waiting approval ends the wait, so the steps behind it don’t run. Fix: run the workflow again for that record. Next time, use Approve or Decline instead of deleting.
Why: the page couldn’t load. Fix: click Try again. If only some sources failed, you’ll see a notice naming them, and everything else is still shown.
Why: the change to a switch didn’t save. Fix: try again. If the page says “Couldn’t load preferences — please refresh the page.”, reload it.
Why: the three Personal notifications switches are disabled because they don’t change notification delivery yet. Fix: mute the browser tab to silence the new-message sound.
Why: the comment was deleted, or you’re not a member of the workspace it’s in. Fix: ask a member of that workspace to invite you.
Public workflow and List Access request notifications use the source workspace. For a requester outside that workspace, approve workspace membership first; resource access remains a separate approval. Trying to approve the resource first shows “A workspace admin must approve membership first. Resource access needs a separate approval.” The requester receives an in-app confirmation with a link to the resource when access is granted, or a decline notification.

Shared meetings

Shared meeting links provide full, permanent viewing access, so visitors do not request an upgrade and owners/admins do not receive new meeting-access approval requests. See Share publicly. After a Standard workspace’s trial (started before November 2026) ends, Ask an admin requests a subscription instead of more credits. Owners and admins receive [member] asked you to start a subscription with an Open Billing link. Remaining credits are kept; adding credits alone does not restore paid work.