Reply action

Push Existing Contact to Campaign (Reply.io)

Push an existing contact to a selected campaign

Run in Studio →All Reply actions
Reply logoReply
reply-push-existing-contact-to-sequence
integrationReturns in secondsLight tier
Input

What it needs.

Map each field to a column in your table. Optional fields can stay empty.

FieldType
  • campaign_id
    The ID of the campaign to which the contact should be pushed.
    dynamic_select
  • email
    The email address of the existing contact.
    string

When to use this.

The "Push Existing Contact to Campaign" action in Reply.io allows users to seamlessly integrate their existing contacts into targeted marketing campaigns. This action requires two key input parameters: the campaignId, which identifies the specific campaign for the contact, and the email address of the existing contact to be pushed. It is important to note that the contact will only be moved if they are not currently enrolled in any active campaign. Upon successful execution, the action returns a unique pushed prospect ID, enabling users to track the contact's status within the campaign. This functionality is particularly useful for marketing teams looking to streamline their outreach efforts and ensure that valuable contacts are effectively engaged in their campaigns. As part of the integration category, this action enhances the efficiency of contact management within marketing workflows.

Output

What it returns.

Every field this action writes back to the row. Click a line to expand nested objects.

FieldType
  • push_prospect_id
    Push Prospect Id
    string
Workflow

How this fits a workflow.

Trigger → Push Existing Contact to Campaign (Reply.io) → enrich → push to your CRM. You set it up once; after that it runs without you.

  1. Step 1TriggerNew row, form submit, or schedule.
  2. Step 2Push Existing Contact to Campaign (Reply.io)The Reply action runs.
  3. Step 3EnrichWaterfall fills missing fields.
  4. Step 4Push to CRMHubSpot / Pipedrive / Zoho CRM / GoHighLevel.

Two actions you can chain after this one:

Push Existing Contact to Campaign (Reply.io)Delete Contact By ID (Reply.io)Create Contact and Push to Campaign (Reply.io)
Reliability

Throughput & reliability.

How fast it drains a table, and what happens when the upstream provider has a bad day.

  • Per-minute limitNo public cap
  • Per-day limitPlan-defined
  • RetriesAutomatic w/ backoff
  • Failed lookupsZero credits

Who runs this

GTM EngineerRevOpsAgency

Light tier. See pricing; per-action credit cost is private.

Related

More Reply actions.

FAQ.

Mostly. Fast actions fill the cell in a few seconds. Long-running ones run in the background and write back to the row when they finish, so you can close the tab.

No. A failed lookup costs zero credits. When a provider misses or times out, the waterfall moves to the next one and you only pay for the match you actually got.

No. Run it on one cell, on a selection, on the whole table, or on a schedule. Same action either way.

HubSpot, Pipedrive, Zoho, and GoHighLevel are bidirectional, with Salesforce coming soon. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Push Existing Contact to Campaign (Reply.io) in 60 seconds.

Connect the account, drop the action on a column, run it on your rows.

Start free →All Reply actions