Floworks

A short fixed list of connectors with no way to add your own. Named: Gmail and Outlook for sending, LinkedIn for social outreach, Calendly and Google Calendar for booking, and HubSpot with Salesforce for CRM, the latter gated to annual plans. The agents take authenticated action rather than reading alone: they send from connected mailboxes, act inside LinkedIn, book into calendars and write back to the CRM. No public API, no webhook and no custom connector is documented anywhere on the site, so a buyer whose stack is not on the list has no documented path.

Sourcefloworks.ai/how-it-works and site navigationread 2026-09-01

The platform carries a documented five-step motion end to end: connect mailboxes and LinkedIn with warmup, define the ICP and generate leads, research prospects and write personalized messages, launch the campaign with an uploaded FAQ and generated playbook, then run automatically sending messages and booking appointments.

Several named agents divide the work between them, with Jesse researching, Alisha and Linda writing and sending across email and LinkedIn, and Dan handling CRM updates.

The control flow itself is not documented; no branching or conditional paths, no retry or error handling and no routing surface the customer can inspect or configure appears on any page, and the reply-triggered escalation from email to LinkedIn is described in outcome terms rather than as configurable logic.

Sourcefloworks.ai/how-it-worksread 2026-09-01

The buyer points the agent at their own material through a documented ingestion step. At campaign launch the customer uploads an FAQ and describes their product, and the platform produces an AI-generated personalized playbook the agents then work from, so prospect questions are answered from material the customer supplied rather than from the model alone. Prospect-side research runs separately across the web and a contact database. The FAQ upload is the only documented ingestion route, and no other document types are named.

Sourcefloworks.ai/how-it-works campaign launch and personalization stepsread 2026-09-01

Autonomy is the stated design and no approval step sits in front of it. The vendor's own five-step workflow ends by telling the customer to let the system run automatically, sending messages and booking appointments, and the product is marketed as a fully autonomous AI SDR. What the customer sets is upstream: the ICP, the product description, the uploaded FAQ and the generated playbook. Nothing lets a buyer mark actions as requiring sign-off, name who signs off, or hold a message pending review, and no draft queue or approval surface appears in the workflow or the site navigation.

Sourcefloworks.ai/how-it-works automate and monitor stepread 2026-09-01

One attestation the vendor does not contradict, and no access controls: the compliance page shows ADA CASA Tier 2 as certified. SOC 2 Type 2 and ISO 27001 are disputed between the vendor's own pages, the compliance page heading them as audits currently under way while the home page calls the company SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant, so neither can be relied on yet. No SSO, roles or permissions the buyer operates are documented.

Sourcefloworks.ai/complianceread 2026-10-01

Campaign-level monitoring is documented as the fifth step of the product's own workflow, automate and monitor, and the site reports open rate, response rate, click-through on opened emails and scheduling rate as the measures a customer watches. The Sage agent is positioned for sales data analysis, pipeline forecasting and campaign optimization. That is aggregate reporting; nothing documents a per-run trace showing which sources the research agent consulted, why a particular message was written, or what each agent did in sequence, and no execution log or audit surface is documented.

Sourcefloworks.ai/how-it-works and homepage metricsread 2026-09-01

State persists across a campaign rather than within an exchange: the customer uploads an FAQ and product description at campaign launch and the agents draw on it thereafter, lead lists are uploaded or synced and held, an AI-generated playbook is produced and reused across the campaign, and reply history carries the follow-up sequence forward from email to LinkedIn. No memory layer with a stated scope or lifetime is documented; nothing says what is retained between campaigns, for how long, or whether it is scoped per campaign or per workspace.

Sourcefloworks.ai/how-it-works campaign launch stepread 2026-09-01

Delivered only as a cloud native SaaS platform with no self host, on premises, or in VPC deployment option documented.

Sourcefloworks.airead 2026-10-01

Packaged assets ship in two forms. Named role agents aimed at named jobs: Alisha for outbound sending, Jesse for research and lead sourcing, Linda for LinkedIn, Sage for RevOps analytics and forecasting, Dan for CRM hygiene and inbox management, with Sam for phone calls listed as coming soon. And an Email Playbooks section published in the site navigation, alongside an AI-generated playbook produced per campaign. The agents are the product's components rather than a catalog a buyer selects from, and no adoptable templates are documented inside the Email Playbooks section.

Sourcefloworks.ai navigation and how-it-worksread 2026-09-01

No person has to start each step. Jesse finds prospects on intent signals, and Alisha automatically follows up based on prospect behavior and engagement, with a missed email reply moving the prospect to a LinkedIn touch.

Sourcefloworks.airead 2026-10-01

Runs on the fixed proprietary ThorV2 model with no user facing model choice, bring your own key, or routing gateway.

Sourcefloworks.airead 2026-10-01

No public API, SDK, or MCP server is documented; ThorV2 is described in a research paper but not exposed as a developer platform.

Sourcefloworks.airead 2026-10-01

No user facing agent testing, debugging, or evaluation product is documented; the Sage agent provides campaign analytics rather than an evaluation framework.

Sourcefloworks.airead 2026-10-01

A dedicated LinkedIn agent, Linda, runs connection requests, messages and meeting scheduling inside LinkedIn alongside the email channel, with LinkedIn connected and warmed at setup. That is the agent acting inside an interface the vendor does not control. The vendor's own pages do not state how those actions are executed. Everything else runs over connected mailboxes, calendars and CRM, which are programmatic routes.

Sourcefloworks.ai/how-it-works setup and personalization stepsread 2026-09-01