ACTION_ID: plusvibe_add_leads_to_campaign NAME: PlusVibe: Add Leads to a Campaign CATEGORY: Outreach CREDITS: 0 Add a lead to a PlusVibe campaign inside a chosen workspace, with optional overwrite of an existing lead and campaign-level custom fields. PREREQUISITE: PlusVibe account connection — the user must create it in the Floqer UI (Connections page); an agent cannot. Without it the action fails the row with a connection / authentication error. Confirm it exists before configuring. 1. INPUTS workspace_id (dynamicDropdownFirst, required) Workspace ID. The ID of the workspace where you have the campaign campaign_id (dynamicDropdownSecond, required) Campaign ID. Campaign ID where you want to add the lead should_overwrite (radio, optional) Should Overwrite. If true, existing lead will be updated with the provided fields while retaining any unspecified fields. lead_fields (dynamicJsonArray, required) Lead Fields. Fields for the lead (email compulsory) custom_fields (raw_array, optional) Custom Fields. Enter the custom fields for the plusvibe lead in the selected workspace 2. OUTPUTS status (string) — Status/Response of the request 3. HOW TO CONFIGURE Two cascading dropdowns — resolve the workspace first, then pass it as context when resolving campaigns: POST .../options/workspace_id (body: {}) POST .../options/campaign_id (body: { "context": { "workspace_id": "" } }) POST .../options/lead_fields (body: {}) Configure Action body: { "inputs": { "workspace_id": "", "campaign_id": "", "should_overwrite": true, "lead_fields": [ { "name": "email", "value": "{{person_work_email_waterfall_01ab.work_email}}" }, { "name": "first_name", "value": "{{input.first_name}}" }, { "name": "company_name", "value": "{{input.company_name}}" } ], "custom_fields": [ { "name": "icebreaker", "value": "{{llm_models_01cd.generated_content}}" } ] } } Field-by-field: - workspace_id PlusVibe workspace. Required before campaigns can be listed. - campaign_id Campaign within that workspace. - should_overwrite `true` updates an existing lead with the supplied fields and keeps everything you did not specify; `false` leaves an existing lead untouched. - lead_fields `[{name, value}]`. `email` is mandatory — PlusVibe rejects the call without it. - custom_fields Custom fields defined on the selected workspace. 4. KEY NOTES - `campaign_id` cannot be resolved without `workspace_id` in the request `context` — calling it bare returns a 400 naming the missing key. - `lead_fields` must contain an `email` entry. The action fails at run time if the resolved email is empty, so gate with `run_if` on `work_email is not empty`. - `should_overwrite` is a boolean — pass real `true` / `false`, not the strings `"true"` / `"false"`. - Only `status` is returned; there is no PlusVibe lead ID to chain from. 5. WHERE IT FITS IN A WORKFLOW Pattern: person_work_email_waterfall -> person_work_email_verification_by_zerobounce -> filter (status is valid) -> plusvibe_add_leads_to_campaign. 6. WHEN TO USE Use plusvibe_add_leads_to_campaign when PlusVibe runs the cold-email sequence and Floqer supplies the enriched, verified leads. 7. WHEN NOT TO USE Need Instantly as the sending platform -> action-detail/instantly_add_to_campaign.txt Need ReachInbox as the sending platform -> action-detail/reachinbox_add_leads_to_campaign.txt Last updated: 2026-08-03.