ACTION_ID: gong_add_prospect_to_flow NAME: Gong: Add prospect to Flow CATEGORY: Outreach CREDITS: 0 Assign one Gong prospect per row to a Gong Engage flow (Gong's sequence). The flow owner then gets the flow's to-dos (emails, calls, LinkedIn steps) in Gong. PREREQUISITE: Gong connection, which the user must create in the Floqer UI (Connections page); an agent cannot. OAuth connections made before the flow scopes were added must be reconnected. The customer's Gong account must also have a CRM connected: Gong Engage finds prospects by CRM record ID, so without a connected CRM every row fails. Confirm both before configuring. 1. INPUTS gong_flow_id (string, required) Gong Flow ID. The flow to assign the prospect to. Copy it from the flow's URL in Gong. gong_prospect_crm_id (string, required) Gong prospect CRM ID. The record ID of a Contact or Lead in the CRM connected to Gong (for a HubSpot contact, its Record ID). Not an email. gong_flow_owner_email (string, required) Gong flow owner email. The Gong user who owns this flow instance and receives its to-dos: the rep doing the outreach, not the CRM record's account owner. This user must hold a Gong Engage seat. 2. OUTPUTS flow_instance_id (string) Gong's ID for this prospect's enrolment in the flow. flow_instance_status (string) The state the enrolment landed in. flow_name (string) The name of the flow. 3. HOW TO CONFIGURE Configure Action body: { "inputs": { "gong_flow_id": "", "gong_prospect_crm_id": "{{hubspot_upsert_object_01ab.id}}", "gong_flow_owner_email": "rep@company.com" } } Field-by-field: - gong_flow_id Required. Pass as a quoted string; flow IDs are long numbers. - gong_prospect_crm_id Required. Usually a reference to a CRM step's record ID: `id` from hubspot_upsert_object, `record_id` from salesforce_upsert_record. All-digit IDs (HubSpot) are fine. - gong_flow_owner_email Required. Must be a valid email of a user in the customer's Gong workspace who holds a Gong Engage seat. 4. KEY NOTES - Engage seats are per user. If the flow owner has no Engage seat, the row fails with Gong's message "User with the given email does not have an Engage license". A Gong admin fixes it by assigning the user an Engage seat (Admin center > Settings > People > Team members), or the workflow uses an owner who already has one. - No options resolvers: there is no flow picker or owner picker. Read the flow ID from the flow's URL in Gong, or from a sheet input column. - The prospect must already exist in the CRM connected to Gong. A record Gong has not synced yet is refused. - Gong can answer "OK" while refusing the prospect. The action reads Gong's result, so a refused prospect fails the row with "Gong did not assign the prospect: ". A green cell means the prospect really is in the flow. - "No CRM integration for the company" means the customer's Gong has no CRM connected. Nothing in Floqer fixes it; a Gong admin must connect the CRM in Gong. - A missing flow fails the row with Gong's own message, or "Gong flow was not found or has been deleted". - An expired OAuth token is refreshed once automatically. If that fails, the row says to reconnect Gong. A missing-permission error also means the user must reconnect Gong. - Rate limits are retried automatically. - Blank inputs or an invalid owner email fail the row before anything is sent to Gong. 5. WHERE IT FITS IN A WORKFLOW Pattern: find or enrich people -> filter -> hubspot_upsert_object or salesforce_upsert_record (get the record ID) -> gong_add_prospect_to_flow. Terminal step. 6. WHEN TO USE Use gong_add_prospect_to_flow when the customer runs outreach in Gong Engage and wants qualified people enrolled in a flow automatically. 7. WHEN NOT TO USE The person is not in the CRM yet -> create them first: action-detail/hubspot_upsert_object.txt or action-detail/salesforce_upsert_record.txt Need an Outreach sequence or a Salesloft cadence instead -> action-detail/outreach_add_prospect_to_sequence.txt -> action-detail/salesloft_add_person_to_cadence.txt Last updated: 2026-10-04.