# Add contacts to Jounce from another app

> **Short answer:** In Zapier, choose Jounce as the Zap’s action, pick Create or Update Subscriber, and map the email plus any names, segments, or custom fields. Jounce adds the person, or updates them if the email is already in your contacts.

When you're done, each run adds one person to your contacts, or updates them
if they're already there. You need Jounce connected to Zapier first; see
[Connect Jounce to Zapier](https://help.jounce.com/integrations/zapier/connect-jounce-to-zapier).

1. On Zapier, build the Zap's trigger in the other app, then add an action
   and choose Jounce.
2. Pick **Create or Update Subscriber**.
3. Choose your Jounce connection. It carries your workspace's name.
4. Map **Email** from the trigger's data. Map **First name** and **Last
   name** if the other app has them.
5. Pick the **Segments** to add them to, and fill **Custom fields** with any
   extra details to keep on the contact's page.
6. Choose whether to **Send a confirmation email first**. The field's own
   line reads _When yes, a brand-new subscriber starts as pending and becomes
   subscribed only after confirming. Needs the confirmation email set up in
   Jounce_.
7. Test the action, find the person in **Contacts**, and turn the Zap on.

## The other actions

The other four actions each take an **Email**. They do what their names say:
**Add Subscriber to Segment**, **Remove Subscriber From Segment**,
**Unsubscribe Subscriber**, and **Find Subscriber**; see
[What a Zap can do with Jounce](https://help.jounce.com/integrations/zapier/what-a-zap-can-do-with-jounce).

## What happens next

- The person appears in **Contacts** with **API** as their Source. Their
  status is Subscribed. If you chose to send a confirmation email first, it's
  Unconfirmed until they click the link.
- Someone already in your contacts is updated, never added twice. Names and
  custom fields change, segments are added, and their status stays as it
  was.
- Custom fields you map are saved on the person's page, even ones new to your
  workspace. One named like a built-in field, such as _First Name_, isn't
  saved as a field of its own: it counts as the real name when you didn't map
  one, and anything else by such a name is left out.
- To send a confirmation email first, your workspace needs to have one. A new
  workspace starts with one; see
  [The Opt-in setup page](https://help.jounce.com/forms/confirmation-and-opt-in/the-opt-in-setup-page).

- If a run left someone out, its details in Zapier show Jounce's own reason;
  see
  [Why didn't my Zap add someone to Jounce?](https://help.jounce.com/integrations/zapier/why-didnt-my-zap-add-someone-to-jounce).

## Next step

Send the other way too: [Start a Zap when someone joins, unsubscribes, or lands in a segment](https://help.jounce.com/integrations/zapier/start-a-zap-when-someone-joins-unsubscribes-or-lands-in-a-segment).

## Also answered here

- “send form entries to jounce with zapier”
- “zapier double opt in jounce”
- “add someone to a segment with zapier”

---

Updated 2026-10-26 · https://help.jounce.com/integrations/zapier/add-contacts-to-jounce-from-another-app
