From Connections, choose Salesforce and authorize through Salesforce's own OAuth. Read access covers accounts, contacts, opportunities, and activity; it lets the queue understand your pipeline without being able to change it.
The record rule: flo.space never edits a record unattended. Stage changes, field updates, and logged activity are prepared actions that show the record as it stands now, the change proposed, and the message that prompted it. Write access is a second, explicit grant, and even after it every change is approved one at a time.
What to expect in the queue: stage moves drafted from threads that already settled them, activity logged from real replies, close dates corrected when a customer pushes a timeline, and follow ups drafted for opportunities that have gone quiet. Where no confident record match exists, the action says so rather than guessing.
Pair it with the inbox for the combination most teams start with; the Gmail + Salesforce page covers that flow end to end.