ACTION_ID: reachinbox_add_leads_to_campaign NAME: ReachInbox: Add Leads to a Campaign CATEGORY: Outreach CREDITS: 0 Add a lead to a ReachInbox campaign, with optional custom fields for template personalisation. PREREQUISITE: ReachInbox 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 campaign_id (dynamicDropdown, required) Campaign ID. The ID of the campaign you want to add the lead to email (email, required) Email. The email of the lead you want to add to the campaign first_name (string, optional) First Name. The first name of the lead last_name (string, optional) Last Name. The last name of the lead company_name (string, optional) Company Name. The company name of the lead custom_fields (raw_array, optional) Custom Fields. Any custom fields you want to add to this lead 2. OUTPUTS status (string) — Status/Response of the request 3. HOW TO CONFIGURE Configure Action body: { "inputs": { "campaign_id": "", "email": "{{person_work_email_waterfall_01ab.work_email}}", "first_name": "{{input.first_name}}", "last_name": "{{input.last_name}}", "company_name": "{{input.company_name}}", "custom_fields": [ { "name": "icebreaker", "value": "{{llm_models_01cd.generated_content}}" } ] } } Field-by-field: - campaign_id ReachInbox campaign to enrol the lead in. - email Required. The lead key on the ReachInbox side. - custom_fields `[{name, value}]` merge variables for the campaign's email templates. 4. KEY NOTES - `campaign_id` has no dynamic-options resolver yet — Get Action Field Options returns a 400 for it. Copy the campaign ID from the ReachInbox UI and pass it as a literal (or wire it from a sheet input). - `email` is required and is what ReachInbox de-duplicates on; re-running the same row updates the existing lead rather than creating a second one. - Only `status` is returned — no ReachInbox lead ID. - Custom-field names must already exist on the campaign. Unknown names are dropped silently by ReachInbox rather than rejected. 5. WHERE IT FITS IN A WORKFLOW Pattern: person_work_email_waterfall -> llm_models (personalisation) -> reachinbox_add_leads_to_campaign. Terminal step. 6. WHEN TO USE Use reachinbox_add_leads_to_campaign when ReachInbox is the sending platform for the campaign. 7. WHEN NOT TO USE Need PlusVibe as the sending platform -> action-detail/plusvibe_add_leads_to_campaign.txt Need Smartlead as the sending platform -> action-detail/smartleads_add_to_campaign.txt Last updated: 2026-08-03.