What flo.space prepares with Salesforce
Reads the record behind the conversation so every prepared action cites the real account, not a guess.
- Prepare the Salesforce record update a conversation just made necessary
- Draft the next touch on a deal that has gone quiet
- The record changes when you approve it, and not before
What it reads, and what it can write
Reads · read-only to start
Only the Salesforce data you connect, within the OAuth scopes you approve. flo.space reads the context it needs to prepare an action and nothing beyond it.
Writes · only on approve
Nothing writes back to Salesforce until you approve it. On approval, flo.space performs the exact action you reviewed, and logs it to the audit trail.
Salesforce in your stack
flo.space groups Salesforce under crm & pipeline. Connect it and the actions it informs land in the same queue as everything else, each one carrying the records it was built from and the reasoning behind it, waiting on your approval.
What flo.space drafts against your records
The record-keeping nobody has time for, prepared from what actually happened: stage and field changes proposed when a thread says the deal moved, with the sentence that justifies them quoted on the card; logged activity, so the history a new rep inherits is the real conversation rather than a blank timeline; contact and account updates when a reply reveals a new decision-maker or a changed address; and the follow up an idle opportunity implies, drafted into the thread it belongs to and priced from the record rather than from memory.
One boundary, stated plainly: flo.space is not a CRM and does not want to be. It does not replace your reporting, your forecasting, or your admin console. It reads the record to keep prepared actions honest, and it proposes the changes a conversation has already made true. Every one of those changes waits for a person.
Connecting Salesforce, step by step
From your flo.space workspace, choose Salesforce and sign in through Salesforce’s own OAuth. flo.space never sees your password.
Accounts, contacts, opportunities, and activity. Nothing at this step can change a record.
Within a day, prepared actions referencing real opportunities appear in the Action Center, still unable to write.
The first time you approve an action that updates a record, flo.space requests the specific write permission it needs. Every write after that is still one approval at a time.
A worked example
A customer replies "we are good to go, but push the start to the first of next month." flo.space matches the thread to the opportunity, prepares a close-date change and a logged activity, and drafts the confirmation reply. Because the date move changes the quarter, the action is flagged for a deliberate read. The rep sees the current record, the proposed change, and the sentence behind it on one card, approves, and the pipeline reflects the conversation the same morning it happened, not at the end of the month when someone reconstructs it.
Limitations, honestly
flo.space works from what your records and your connected inbox contain: if your opportunities are thin, drafts will need more editing until the record catches up. It does not build reports, manage permissions, write Apex, or administer your org. It does not bulk-update records; fifty stage changes means fifty approvals, quick ones, because that is the product's promise rather than a missing feature. Reference detail lives in the documentation, and the pairwise workflow page for Gmail + Salesforce goes deeper on the combination most teams start with.
Salesforce + flo.space, answered
No. Stage changes, field updates, and logged activity are prepared actions that show the record as it stands, the change proposed, and the message that prompted it. A person approves every one, and write access is a separate grant from the read-only connection.
Accounts, contacts, opportunities, and activity, within the OAuth scopes you approve, read-only at the start. It does not read anything outside the granted scopes, and access is revocable instantly from either side.
It matches to an existing record first and shows which one it matched and why. Where no confident match exists it says so rather than guessing, and creating a new record stays a decision you make.
Logging captures that an email happened. This reads what the email said and proposes the specific record change it implies, with the source sentence attached. You are approving a judgment, not filing an attachment.
Salesforce paired with the rest of your stack
Deep dives on what flo.space prepares between two connected tools.
Connect the rest of your stack
Put Salesforce on approve
Connect Salesforce read only and let flo.space prepare the first wave of actions. Nothing sends until you approve.