Mocca Settings
Mocca Settings
All vendor credentials and switches live on one page in the Desk: Mocca Settings. Open it at /app/mocca-settings, or type Mocca Settings in the Desk search bar. You need the System Manager role; nobody else can see it.
The page has one tab per vendor: Peek Pro, Shopify, Eventbrite, Square, Mailchimp, Meta Ads, Google Ads and Social.
To switch a vendor on
- Open the vendor’s tab.
- Tick Enable
. The vendor’s fields appear. - Fill in the API fields listed on the vendor’s page in this guide (the key or token, and account ids). Webhook secrets can wait: without them the vendor still syncs on a schedule, only its instant updates are refused.
- Click Save.
- Click Test Connection. Mocca makes one read-only call to the vendor and shows the result. A green message means the credentials work; a red one shows the vendor’s error, with any secret blanked out.
If a required field is empty, Mocca refuses to save a vendor as enabled and names the empty fields, for example “Shopify is enabled but these fields are empty: Access Token”. Fill them in, or untick Enable, and save again.
What “Enabled” does
A vendor that is switched on syncs: its scheduled jobs run, its webhooks (instant updates the vendor sends) are accepted, and an administrator can run a manual import.
A vendor that is switched off is off everywhere:
- its scheduled jobs do nothing, and do not show as failed;
- its webhook address answers “not found”, so the vendor’s deliveries are refused;
- manual imports refuse to start.
Switching a vendor back on makes Mocca catch up on what it missed. See Switching a vendor off and on.
Secrets
Keys, tokens and webhook secrets are password fields: after you save, the page shows dots instead of the value, and nobody can read the value back from the screen. Mocca also blanks secrets out of every error message it writes.
To rotate a key
- Create the new key in the vendor’s own dashboard.
- Paste it into the matching field in Mocca Settings and click Save.
- Click Test Connection.
- Revoke the old key in the vendor’s dashboard.
The new key is used from the next sync on. There is no restart and no deploy. The exception is the Peek Pro webhook secret, which needs a second step; see Peek Pro.