ACTION_ID: push_data_to_another_floqer_workflow
NAME: Send data to another Floq
CATEGORY: Floq Tools
CREDITS: 0

Push rows from the current workflow into another Floqer workflow
(a "Subfloq"), invoking it with the data you choose. Use to delegate
work to a sub-workflow or split a long pipeline into smaller,
reusable Floqs.

1. INPUTS

choose_or_create_a_new_workflow (string, required)
  The destination Floq's workflow UUID. Find IDs via List Workflows.
  Must already exist — this action does not create new Floqs.

select_a_list (structured_array, optional)
  A reference to an upstream `structured_array` output. Each item in
  the resolved list invokes the destination Floq once. Omit to send
  a single invocation built from the current row's values.

choose_columns_to_send_to (jsonArray, required)
  Column mapping. Each item is `{name, value}` — `name` matches an
  input column name on the destination Floq's main sheet; `value` is
  what to send (a `{{ref}}`, a literal, or a 3-segment
  `structured_array_reference` like `{{<upstream>.<list>.<column>}}`
  when fanning out via `select_a_list`).

2. OUTPUTS

(no response fields — this action does not emit output. Downstream
steps cannot read values produced by the destination Floq from this
action's output. If you need the destination's results back in the
parent, design the destination Floq to write them to a shared sheet,
e.g. via `push_data_to_sheet`.)

3. HOW TO CONFIGURE

Single-invocation push (one run on the destination Floq per parent row):

{
  "inputs": {
    "choose_or_create_a_new_workflow": "<destination_workflow_uuid>",
    "choose_columns_to_send_to": [
      { "name": "email",        "value": "{{input.email}}" },
      { "name": "company_name", "value": "{{input.company_name}}" }
    ]
  }
}

Fan out a structured_array into one invocation per item:

{
  "inputs": {
    "choose_or_create_a_new_workflow": "<destination_workflow_uuid>",
    "select_a_list": "{{get_employees_by_company_using_apollo_1.list_of_employees}}",
    "choose_columns_to_send_to": [
      { "name": "first_name",   "value": "{{get_employees_by_company_using_apollo_1.list_of_employees.first_name}}" },
      { "name": "last_name",    "value": "{{get_employees_by_company_using_apollo_1.list_of_employees.last_name}}" },
      { "name": "linkedin_url", "value": "{{get_employees_by_company_using_apollo_1.list_of_employees.person_linkedin_url}}" }
    ]
  }
}

Field-by-field:
  - choose_or_create_a_new_workflow  Destination Floq UUID.
  - select_a_list                    Optional. Upstream
                                     `structured_array` to fan out;
                                     each item triggers one
                                     destination invocation.
  - choose_columns_to_send_to        Each `name` matches an input
                                     column on the destination Floq's
                                     main sheet. Unmatched names come
                                     back as `unknown_field` warnings.

4. KEY NOTES

- The destination Floq must already exist. This action does not create
  Floqs implicitly despite the field's display name.
- Map every required input on the destination — missing required fields
  cause the destination run to fail at execution time.
- This action emits no output. If the parent needs results back,
  design the destination to write into a shared sheet via
  `push_data_to_sheet` and read from it later.
- Pushed values land JSON-ESCAPED on the destination: a newline
  arrives as the two characters `\` `n`, and an embedded double
  quote as `\"`. Rows created through `POST .../rows` on the same
  sheet keep their real characters, so a column fed by both paths
  holds two different encodings. Any formula that parses the
  landed value — HTML stripping, JSON.parse, line splitting — must
  unescape first or it will silently see zero newlines. See
  `formula.txt` §4 for the normalizer.
  Verified live 2026-08-05.
- `name` values in `choose_columns_to_send_to` must match input column
  names on the destination Floq's main sheet — the server validates
  each one and surfaces mismatches as warnings on the Configure Action
  response.
- When fanning out via `select_a_list`, use 3-segment
  `structured_array_reference` tokens for per-item column values so
  each invocation gets its own data; row-scoped `{{input.X}}` values
  repeat across every invocation.

5. WHERE IT FITS IN A WORKFLOW

UPSTREAM — what feeds this action
  The current row carries the values you want to send to the
  destination Floq. Those values reach this action via the
  `choose_columns_to_send_to` mapping (each `value` is usually
  `{{input.<field>}}`). When fanning out, an upstream step produces
  a `structured_array` (e.g. an array of contacts on a company row)
  that you point `select_a_list` at.

THIS ACTION
  Invokes the destination Floq once per row (or once per list item
  if `select_a_list` is set), populating its input fields from
  `choose_columns_to_send_to`.

DOWNSTREAM — typical chains
  Sub-workflow fan-out:
    parent row -> push_data_to_another_floqer_workflow -> destination
    Floq runs end-to-end (enrichment, outreach, etc.) per row.
  Multi-stage pipelines:
    stage 1 workflow -> push_data_to_another_floqer_workflow ->
    stage 2 workflow. Use to split a large pipeline into smaller,
    reusable Floqs.

6. WHEN TO USE

Use push_data_to_another_floqer_workflow to delegate work to a
sub-workflow:
  - Fan out: parent workflow processes companies; for each company,
    push its list of contacts into a contact-level Subfloq.
  - Pipeline split: keep a "lead-gen" Floq separate from an
    "outreach" Floq. The first hands off to the second.
  - Reuse: a single Subfloq encapsulates a flow (e.g. enrich +
    verify email) and is invoked from multiple parent workflows.

7. WHEN NOT TO USE

Need to push rows to a sheet, not invoke a Floq
  -> action-detail/push_data_to_sheet.txt

Need to read data from another Floqer table, not push to it
  -> action-detail/lookup_another_floqer_workflow_row.txt

Last updated: 2026-04-30.