CC Rules for Zendesk
Add and remove end-user CCs on tickets with rules. Zendesk triggers can only CC agents; CC Rules CCs requesters' managers, account contacts and any e-mail address, and removes CCs you do not want.
Getting started
- Install CC Rules from the Zendesk Marketplace. There is nothing to fill in.
- Connect. As a Zendesk admin, open CC Rules from the icon in the left navigation bar and click Connect to Zendesk. A window names your account; continue, and approve access. The admin who clicks Connect must be the one who approves.
- Add rules under Rules, and test each one on a real ticket with Test in the editor or under Dry run. Testing never changes a ticket.
- Set up: click Create webhook and trigger, then in Admin Center move the new trigger CC Rules: apply CC rules to the end of your trigger order. From then on, rules apply whenever a ticket is created or updated.
Who can do what
| Action | Who |
|---|---|
| Connect, change rules, dry run, set up, disconnect | Zendesk admins |
| See the rules (read-only) and the ticket sidebar | Agents |
Zendesk signs every load of the CC Rules pages, so the service knows which user is asking and checks with Zendesk that they are an admin before any change. The sidebar evaluates rules in the agent's browser with the agent's own Zendesk access, so it shows nothing about tickets the agent cannot open. To hide the app from some agents, use Role and group restrictions in the app's settings (Admin Center → Apps and integrations → Zendesk Support apps → CC Rules).
Rules
A rule has conditions and actions. With all, every condition must hold; with any, one is enough. A rule without conditions applies to every ticket.
| Condition | Matches when |
|---|---|
| Tag | The ticket has one of the tags (or none of them) |
| Organization | The ticket's organization is (or is not) one of those chosen |
| Ticket form, brand, group | The ticket uses one of those chosen (or none of them) |
| Ticket field | A custom field has a value, or is (or is not) a given value; for drop-downs choose the option |
| Action | What happens |
|---|---|
| CC these e-mail addresses | Each address becomes a CC. Addresses that are not Zendesk users yet are added as end users first, since a CC must be a user. |
| CC the e-mails in a requester's user field | Reads a text user field on the requester, for example "Manager e-mail". Several addresses may be separated by commas, semicolons or spaces. |
| CC the e-mails in an organization field | Reads a text field on the ticket's organization, for example "Account manager e-mails". |
| Remove CCs at these domains | Removes CCs whose address is at the domain or a subdomain of it (gmail.com also removes eu.gmail.com, not notgmail.com). |
| Remove all end-user CCs | Removes every CC who is an end user. Agents stay. |
When several rules match, their actions are combined into one update. A CC that any matching rule adds is never removed by another in the same run. The requester is never added as a CC.
How it works
Set up creates one webhook and one trigger in your account (Admin Center → Objects and rules); running it again checks and repairs them instead of adding copies. The trigger fires when a ticket is created or updated and sends only the ticket number and tags to the CC Rules service, signed with the webhook's secret. The service checks the signature, rejects messages older than five minutes and repeats, reads the ticket through the API, decides which rules apply and updates the ticket's CCs in a separate update with the access an admin granted. New addresses become end users (Zendesk creates them from the CC); existing users are never renamed or changed.
The update is separate on purpose: Zendesk does not change CCs in an update that also adds an internal note. Like any ticket update, it runs your other triggers again; CC Rules ignores its own echo.
After each update CC Rules checks that Zendesk really changed the CCs. If not (CCs turned off, for example), it does not try the same change on that ticket again for 24 hours. If one address cannot be added (a suspended user), the others are still added one by one.
The ticket sidebar
Agents see which rules apply to the open ticket and which CCs the next update will add or remove. Turn it off with the Show the ticket sidebar panel setting.
Limits
- 48 CCs per ticket, as Zendesk allows. Addresses beyond that are skipped and shown as skipped in a dry run.
- CC Rules makes the same change to a ticket at most once an hour. A new change happens at once (a customer copies a private address in a reply: it is removed on that update), but if an agent or another trigger undoes a change, CC Rules makes it again only after the hour, on the next update. This prevents loops with its own update, with other triggers and with Zendesk's webhook retries.
- The CC change shows in the ticket's events as an update through the API by the admin who connected CC Rules.
- Rules see the ticket as it is after all triggers of an update have run, as long as the CC Rules trigger is last in the order.
- 50 rules per account.
- Zendesk's own limits apply: CCs must be enabled (Admin Center → Objects and rules → Tickets → Settings → CCs and followers), and Zendesk allows 30 updates per ticket in 10 minutes.
Data
The CC Rules service runs on Cloudflare. Per Zendesk account it stores, in a Durable Object restricted to Cloudflare's EU jurisdiction: your rules, the access token, the webhook's signing secret and ids, and for up to 24 hours markers naming a ticket number and a fingerprint of a CC change (no addresses). It stores no ticket content, no comments and no user details; ticket data is read when a rule runs and discarded. Requests reach Cloudflare at its nearest location before being handled in the EU. See Privacy.
Frequently asked
Why does CC Rules need an admin to connect?
It updates CCs on any ticket, and creating webhooks and triggers is an admin task in Zendesk.
Can I edit the trigger CC Rules created?
Leave its conditions and actions as they are and keep it last in the trigger order; it only sends a message and changes nothing itself.
How do I stop or uninstall CC Rules?
Under Set up click Disconnect first: it deactivates the trigger, deletes the webhook and revokes CC Rules' access. Then uninstall. If you uninstall without disconnecting, the service notices within a day and does the same and deletes everything it stored for your account. To have your rules deleted after a disconnect, email support@aldorock.com.
Price
39 USD per Zendesk account per month, billed through the Zendesk Marketplace, after a 14-day free trial.
Changelog
- 1.0 (November 2026): first release.
