[workflow]
Oppulence will draft a follow-up. It will not send it under your name until you say so.
If a product can send as you, the default has to be no. The first bad send is the last time a careful team leaves the integration on.
Gmail, Slack, calendar, and HubSpot writes are proposed, checked, and held. A recommended action is a draft with a source. You approve it, edit it, or reject it. The outcome goes back on the ledger.
Local notes and local search do not need approval. Anything that writes to mail, Slack, calendar, or CRM does.
Connections start as reads. You add write scopes when you want drafts that can actually go out.
It is not autopilot email. It is not a sequencer. It is not a promise that the draft is always right. A bounced contact or a person who left still has to be caught by a person, or by the contact check before the approve button is useful.
Read governed actions and the short approval guide.
