Your keys. Your quota. Your inbox.
Leadflow doesn't proxy your data through a shared account. You plug in your own Apify token and your own Google OAuth app — each user's credentials are encrypted at rest and scoped to their account.
Runs the compass/crawler-google-places actor under your Apify account. You control the plan, the concurrency, and the invoice.
- 01Create a free Apify account.
- 02Open Settings → Integrations → API tokens.
- 03Copy the Personal API token and paste it into Leadflow → Settings.
Drafts land directly in your Gmail drafts folder. Because you provide the Client ID + Secret, no other user can ever touch your inbox.
- 01In Google Cloud Console, create an OAuth 2.0 Client (Web application).
- 02Add the Leadflow callback URL shown in Settings as an Authorized redirect URI.
- 03Paste the Client ID and Client Secret into Leadflow → Settings, then click Connect Gmail.
Encrypted at rest
Every token is encrypted with AES-256-GCM before it touches the database. Even the raw row is opaque.
Row-level scoped
Row Level Security policies restrict every credential and every run to the account that created it.
No shared pool
There is no house Apify account and no house Gmail. If your quota isn't used, no one else can use it.