Integration User Contact Insert Fails With CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY and No Debug Logs

Supply the record type explicitly on the create request. For a Salesforce Integration-license user there is no profile default to fall back on and no earlier automation hook to set it, so the request itself must carry the record type.

1. Confirm which user the integration actually authenticates as (check Login History at the time of a failing call). Apply all permission work to that user, not a similarly named one.
2. On the permission set assigned to that user, under Object Settings → Contacts → Record Types, assign the active record type (Individual) with Create on Contact.
3. In the integration's connection configuration, include RecordTypeId in the Contact create request, set once to the fixed Id of the active record type. This is a single static value, not per-record logic, and is the standard pattern for Integration-license users.
4. Drop any id key from create payloads — a create call that specifies an Id is rejected with "The Id field should not be specified" (an empty string is tolerated, but omitting the key is cleaner).
5. Re-run one create; the Contact should insert successfully.

Notes on approaches that do not work for this user type:

• Setting a default record type on the profile is not possible — the Minimum Access - API Only Integrations profile has no Contact object entry and cannot hold a default.
• A before-save flow that stamps the record type does not help, because the record-type validation runs before flows execute.
• The RecordTypeId is org-specific. When promoting to production, look up the production Id of the same record type (Setup → Object Manager → Contact → Record Types) and use that value; the sandbox Id will not match.

The same pattern applies to any object with an active record type that this integration user writes to (for example Opportunity/Donation): supply the correct RecordTypeId on the request and ensure the assigned permission set grants access to that record type.