Campaign → Analytics
Keep recipient status, opens, clicks and campaign activity close to the send that produced them.
Explore Analytics →ReachFlux is not presented as a marketplace of thousands of integrations. Its connection story is focused: sender accounts power campaigns, replies stay attached to conversations, Google Calendar supports authorized meeting scheduling, and campaign activity can continue into the built-in lead pipeline.
For an outreach product, the important question is not how many logos fit on an integrations page. It is whether the systems around a campaign pass the right context at the right time.
ReachFlux currently centers that workflow on sending accounts, replies, its built-in CRM, AI-assisted actions and supported Google Calendar scheduling. We would rather explain those connections precisely than advertise integrations that are not documented in the product.
ReachFlux can distribute recipients across multiple connected sender accounts. Each account can retain its own signature, so the campaign can use the correct sender identity while workload is divided across the configured accounts.
Actual distribution depends on the sender accounts configured for the campaign.
ConversationA lead reaches the meeting stage.
Supported actionAsk for a meeting time or schedule a meeting.
Laravel backendThe application performs the authorized Calendar request.
Users can voluntarily connect Google Calendar through Google's authorization flow. When authorized, ReachFlux can create and manage meeting events as needed for supported scheduling functionality.
Auto-Pilot can evaluate an outreach conversation and select a supported action. The AI does not directly call Google Calendar. The ReachFlux Laravel application performs the authorized Calendar operation.
Read the Google API data explanation →This boundary matters because an AI decision and a third-party API operation are not the same thing.
ReachFlux already links campaign operations to several workflows inside the product. That reduces the need to move basic outreach context between separate systems.
Keep recipient status, opens, clicks and campaign activity close to the send that produced them.
Explore Analytics →Move a meaningful conversation into pipeline stages instead of leaving qualification disconnected from outreach.
Use the supported Google Calendar flow when a conversation reaches the scheduling stage.
Retain lead value, currency, won-revenue and invoice context as the opportunity progresses.
A connection page becomes misleading very quickly when planned integrations are presented as live product capabilities. These boundaries keep the public story aligned with the documented platform.
No “5,000+ integrations” claimReachFlux is not advertised here as a giant app marketplace.
No Salesforce / HubSpot / Pipedrive native-sync claimThose CRM connections are not presented as currently documented capabilities.
No LinkedIn automation claimNo automated connection requests, InMail sequences or profile enrichment are advertised.
No automatic inbox warm-up claimSender connections are not described as a built-in warm-up service.
No automatic SPF/DKIM setup claimReachFlux does not claim to configure provider DNS authentication automatically.
The goal is a precise description of current ReachFlux connection points, not a catalogue of hypothetical integrations.
The documented connection workflow includes configured sender accounts and an optional Google Calendar connection for supported meeting scheduling. Campaign analytics, replies, CRM stages and invoices are built into ReachFlux itself.
Yes. A user can voluntarily authorize Google Calendar access for supported meeting-event functionality. ReachFlux's application performs authorized Calendar operations.
No. Auto-Pilot can classify a conversation and select a supported scheduling action. The ReachFlux backend performs the authorized Google Calendar API request.
This page does not claim those CRM integrations as current documented capabilities. ReachFlux includes its own lead pipeline for managing outreach opportunities.
Yes. ReachFlux supports multi-account campaign distribution and dynamic per-account signatures as part of the sending workflow.
Build an outreach workflow around the connections ReachFlux actually supports today.