Copper

Status	Kind	How you connect
Coming soon	CRM	Enter your Copper account details in bubbl3

Copper isn't offered yet. This page says what it will do and what you can use meanwhile: a Lead URL, or Zapier, Make or n8n.

What it does

Connecting Copper lets bubbl3:

• import People and Leads (both, one kind, a tag, an assignee, or those changed since a date) and get new and changed records as they happen;
• log every text bubbl3 sends or receives, and held or refused texts with the reason, as Note activities;
• keep opt-outs in step through bubbl3's checkbox field, Opted out of texts (bubbl3);
• update fields and tags when a workflow or conversion event asks.

Setup

1. In Copper, open Settings, Integrations, API Keys and generate a key.
2. In bubbl3, open Settings, Integrations, choose Copper and enter the key and the email of the Copper user who made it. bubbl3 checks them with one read call.
3. Choose what to import, check the count and the field mapping. The mobile phone is the number texts go to.
4. Answer How did these leads agree to hear from you?

What you enter	Where to find it
API key	In Copper, Settings, Integrations, API Keys
Copper user email	The email of the Copper user who made the key

bubbl3 adds its checkbox field and four webhook subscriptions when you connect.

Disconnect

Disconnect from the connection page in Settings, Integrations.

• Stops at once: imports, new and changed records, activities and writebacks. bubbl3 deletes its subscriptions in Copper.
• Deleted at once: your API key and the links between bubbl3 contacts and Copper records. Opt-outs still waiting are dropped.
• Kept: contacts imported from Copper, with their messages, labels and consent, unless you tick Also delete the contacts imported from it. Activities, fields and tags bubbl3 wrote stay.
• Deleted later: the updates Copper sent are deleted 30 days after they arrived.

Data shared

From Copper to bubbl3: People's and Leads' names, emails, phones, assignee, company, tags and custom fields.

From bubbl3 to Copper: Note activities for texts; the opt-out field on STOP; fields and tags when you ask; bubbl3's subscriptions.

Scopes and permissions

Copper API keys have no scopes: the key acts as the user who made it. Use a user who can read People and Leads and add activities.

Events

What bubbl3 receives

Event in Copper	In bubbl3
new (person or lead)	New contact. bubbl3 reads the record, imports it and starts "Lead imported from CRM" workflows.
update (person or lead)	Contact updated. bubbl3 reads the record again; starts "CRM contact updated" workflows. The opt-out checkbox ticked opts them out.

What bubbl3 writes back

What	Where it shows in Copper
Text log	A Note activity on the person or lead
Opt-outs	Opted out of texts (bubbl3) ticked
Field updates	The field you chose
Tags	Tags added or removed
Notes	A Note activity from a conversion event

Sending rules that still apply

Copper never texts anyone through bubbl3 itself. Its new and changed contacts can start your workflows, and every workflow text goes through the same checks as a text you send from bubbl3. Nothing in Copper can turn them off.

• Consent. When you connect Copper or create a lead source, you confirm that everyone you send to bubbl3 has agreed to receive texts from you, so its contacts can be texted straight away. bubbl3 never texts a contact who opted out, and a workspace set to text only opted-in contacts texts only them.
• Opt-out. Replying STOP opts a contact out at once. bubbl3 also records it in Copper.
• Quiet hours. No texts from 8:00 PM to 9:00 AM in the contact's own time zone (from the phone's area code). A text due then waits until the morning.
• Pacing. Each line texts at most 15 new contacts an hour and 50 a day (fewer while a new line warms up), and spaces texts 20 to 90 seconds apart. A big import or batch is queued and sent as the limits allow, never dropped.
• First messages. Until a contact replies, a text can't include links, photos or files, phone numbers or email addresses, must be 300 characters or fewer, and at most 3 texts go out.

What Copper is told when bubbl3 doesn't send

A Note activity on the record says the text wasn't sent, with the reason. A held text gets a note saying when it's scheduled.

Reason	Code	What you see
A link before the contact replies	pre_reply_link_blocked	Not sent: "Links can't be sent until the contact replies"
A photo or file before the contact replies	pre_reply_media_blocked	Not sent: "Photos and files can't be sent until the contact replies"
A phone number before the contact replies	pre_reply_phone_blocked	Not sent: "Phone numbers can't be sent until the contact replies"
An email address before the contact replies	pre_reply_email_blocked	Not sent: "Email addresses can't be sent until the contact replies"
A first message that is too long	pre_reply_too_long	Not sent: "First messages must be 300 characters or fewer"
Too many texts without a reply	pre_reply_message_limit	Not sent: "Already sent 3 texts without a reply. Wait for the contact to reply"
The same text to too many people today	identical_text_limit	Not sent: "This exact text went to 20 people from this line today"
The line is paused after unanswered texts	unanswered_streak_limit	Not sent: "This line is paused after too many unanswered texts"
The contact opted out	contact_opted_out	Not sent: "The contact opted out of texts"
The workspace texts only opted-in contacts	consent_required	Not sent: "This workspace only texts contacts who opted in"
No line can reach the contact	line_unavailable	Not sent: "bubbl3's line for this contact isn't available"
Quiet hours	quiet_hours	Held: "Scheduled for 9:00 AM America/Chicago, quiet hours"
The line's daily limit	daily_new_contact_cap	Held: "Scheduled for Oct 15, 9:00 AM America/Chicago: today's limit for this line is reached"
The line's hourly limit of new contacts	hourly_new_contact_cap	Held: "Scheduled for 2:00 PM America/Chicago: this hour's limit of new contacts for this line is reached"

The numbers are the default limits; a line's own limits change them. bubbl3's other checks (no phone number, a number that doesn't match) have their own plain reasons.

Limits and known gaps

• A checkbox as the consent field opts out everyone not ticked. If you choose "A field in the CRM records it" and name a checkbox custom field, every person whose box isn't ticked reads false and is opted out in bubbl3 (not copied to your other CRMs). Name a field that's empty until someone answers, or a dropdown with a real "No".
• Copper allows 180 requests a minute per user; bubbl3 uses at most 75 calls a minute per connection. A notification naming many records is read 60 a minute; none are dropped.
• Copper doesn't sign webhooks, so bubbl3 checks its own random key in each notification, made new each time you connect.
• Lists, stages and opportunities aren't imported.

Troubleshooting

• "The provider didn't accept these credentials". Check the key and that the email is the key's own user.
• The connection needs attention. The key was removed in Copper. Connect again with a new key.