CleverReach

CleverReach

This connector uses the CleverReach REST API v3 (https://rest.cleverreach.com/v3) of CleverReach, the German email marketing service: groups (receiver lists) and their receivers (subscribers) with attributes, tags and events, double opt-in mails, the blacklist and bounces, mailings as drafts with previews, and reports of sent mailings. It does not send a mailing to its list: CleverReach grants that only with an extra scope on request, so the final send happens in CleverReach.

Setup (about 10 minutes, CleverReach admin)

1. In CleverReach open Account, Extras, REST API and create an OAuth app. Select the scopes Recipients (oa_receivers), Reports (oa_reports), Forms (oa_forms) and Emails (oa_mailings).
2. Register the redirect URL https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP server URL>/api/mcp-oauth/callback when you host AnythingMCP yourself.
3. Copy the app's Client ID into CLEVERREACH_CLIENT_ID and its Client Secret into CLEVERREACH_CLIENT_SECRET, leave CLEVERREACH_REFRESH_TOKEN empty and install.
4. Click Authorize with Provider on the connector and sign in to CleverReach. Tokens are renewed automatically. Run cleverreach_whoami to check.

Workflow

• Lists: cleverreach_list_groups, cleverreach_get_group, cleverreach_get_group_stats, cleverreach_create_group, cleverreach_update_group, segments with cleverreach_list_group_filters.
• Receivers: cleverreach_list_group_receivers, cleverreach_get_receiver (by id or email, with group_id for group fields), cleverreach_find_receivers (temporary filter across groups), cleverreach_list_receiver_groups, cleverreach_list_receiver_events.
• Adding and changing receivers: cleverreach_create_receiver for one, cleverreach_upsert_receivers for many (matched by email), cleverreach_update_receiver, cleverreach_activate_receiver, cleverreach_deactivate_receiver. cleverreach_delete_receiver is installed switched off.
• Double opt-in: create the receiver with registered set to now and activated "0", then cleverreach_send_form_mail with type activate and the form id from cleverreach_list_forms; CleverReach activates the receiver when the link is clicked. Without registered and activated a new receiver is active at once, which needs consent you can prove.
• Tags and fields: cleverreach_add_receiver_tags, cleverreach_remove_receiver_tags, cleverreach_list_tags; attributes with cleverreach_list_attributes and cleverreach_create_attribute (global, or per group with group_id).
• Do not mail: cleverreach_list_blacklist, cleverreach_get_blacklist_entry, cleverreach_add_to_blacklist, cleverreach_remove_from_blacklist; bounces with cleverreach_list_bounces and cleverreach_list_bounced_receivers.
• Mailings: cleverreach_list_mailings, cleverreach_get_mailing, cleverreach_list_templates, cleverreach_list_mailing_channels, then cleverreach_create_mailing (a draft for groups or a filter), cleverreach_update_mailing, cleverreach_send_mailing_preview to the account's own users, cleverreach_get_mailing_links.
• Results: cleverreach_list_reports, cleverreach_get_report, cleverreach_get_report_stats (by mode), cleverreach_list_report_receivers (who opened, clicked, bounced or unsubscribed).

Consent and writes: receivers are personal data under the GDPR. Only add or activate addresses with documented consent, show the user what will change and wait for a yes before writes.

Reading the answers: ids are numbers sent as strings. Receiver tools accept the receiver id or the email address. Times (registered, activated, deactivated, stamp, report dates) are Unix timestamps in seconds; 0 means not set. A receiver is active in a group when activated is set and deactivated is 0. global_attributes apply in every group, attributes in one group.

Paging: pages start at 0. Receivers take pagesize (up to 5000) and page; bounces up to 500 per page; mailings limit and page (paging only when state is not all). A page shorter than the page size is the last one.

Errors: the answer carries an error code and message. 401 means the token expired or was revoked (authorize again), 403 that the OAuth app lacks the scope for that area, 404 an unknown id or an address not in that group (or not blacklisted), 400 invalid data such as a wrong attribute name or timestamp.