Connections that are really ready
What a payment engine, an accountant’s engagement, an API client, a certificate, an email rule and the Teams, YouTube and LinkedIn connections need before they work — and what the screens now refuse.
| Screen | What it needs |
|---|---|
| Platform › Payments › Payment Engines | A Clearing account: every payment taken posts there. Without one the engine cannot be saved as configured or connected, takes no capture or card sale, and Readiness says no clearing account (or no API secret, disabled, ready). |
| Platform › External Accountants › Accountant Access | An end date. Left empty on an invite it is twelve months from today; at most three years ahead; it cannot be cleared to “never”. Change end date moves it; a past day ends the engagement. |
| Platform › Published API › API Clients | An active client must have Acts as — the user it acts for. Save it suspended until you know. The key is shown once when issued; the Key column shows its last four only for a key that was issued. |
| Platform › Integration › Certificates | A certificate that has expired is refused on save, and an expired or inactive one cannot be attached to a connection: add the renewal. |
| Platform › Email › Email Rules | Who receives it is a plain list, one to a line: an email address, actor, supplier, role: buyer, field: requested_by, person: assignee or user: <id>. The event must exist (Email Events, or <module>.<screen>.created, .updated, .status_changed). |
| Platform › Integration › Connections | An https:// endpoint (http:// is refused) that is not a template (example--sandbox, your-domain). The list and record say why the last test failed. |
Teams, YouTube and LinkedIn
- Microsoft Teams calls and meetings run through CRM › Interaction Centre › Connected Channels, not a Platform connection. Its Test (Prove the credentials work) names every missing piece: Tenant id, Client id, Client secret (the Value, not the Secret ID) and the Graph application permissions with admin consent; it reads Ready or Not ready for Teams.
- YouTube (Platform › Social Channels › Social Accounts › YouTube › Connect): an API key from Google Cloud with the YouTube Data API v3 enabled. A pasted channel address becomes its channel id.
- LinkedIn Page: the Organisation ID is a number from linkedin.com/company/<number>/admin/ (the whole address can be pasted), a developer app with the Community Management API, and an access token (60 days) created by a Page administrator with r_organization_social. Leave API version empty: a current LinkedIn version is used, and a typed one (YYYYMM) stops working when LinkedIn retires it. Test reads the page’s posts as listening will; a refusal quotes what LinkedIn answered and says what to change. Handle is display only.
- The Connect dialog shows What you need, and where to get it, and where each field comes from.
There is one set of Email Settings per company: open it and Edit, rather than New. Refused API calls now appear on the API Call Log, and webhook counts (Queued, Sent, Not sent, Waiting) come from the deliveries.