A private integration connects an authorized application to a specific CentriCRM account. Treat access as a business decision: name the owner, define the work it may perform and grant only the permissions needed. Seeing API documentation does not establish that your account has every API feature.
Before you beginHave an administrator confirm the intended business, available integration controls and the developer responsible for the connection. This checklist prepares the request; creating credentials or enabling a live connection requires the account owner's authorization.
Step by step
- Write down the outcome in plain language, such as reading contact details for an approved internal report. List the records the integration needs to read or change and the business it belongs to.
- Choose a responsible business owner and technical contact. Agree on how the integration will be disabled when its purpose ends or ownership changes.
- Ask the developer to identify the required API areas, account context and exact scopes using the official reference. Separate read access from permission to create, update, delete or send communications.
- Have an administrator confirm that Private Integrations is available and permitted for the account. If the control is absent, resolve access and entitlement before assuming a different account's instructions apply.
- Agree on a server-side secret store and an authorized handoff method before any token is generated. Tokens belong outside public code, browser fields, source control, screenshots and support messages.
- Plan a narrow test using controlled records, including the expected result and what should happen when access is missing or a different business is selected. Approve live writes and messages separately from a read test.
- Record the integration's purpose, business, owner and granted scopes without recording the token. Keep a rotation and revocation plan with the deployment owner, and verify the connection after any credential change.
Expected result
The administrator and developer have an agreed access request, secure credential-handling plan and controlled verification procedure for one identified business.
Troubleshooting
- If the integration menu is missing, confirm account permissions and availability with the administrator rather than borrowing another business's credential.
- If the developer requests broad access, ask which required operation needs each scope before approval.
- If a credential is exposed, notify the authorized administrator promptly and follow the account's revocation or rotation process. Do not paste the credential into a support ticket.
Supporting documentation
These links open the provider’s documentation. Availability and permissions depend on your account.
More guides
Create and verify a contactKeep a single useful customer record, check the business context, and confirm your changes saved.
Review and respond to a conversationFind the right thread, review its history, and check the channel and recipient before responding.
Check a website lead form before launchFollow a controlled submission from the public form to the correct contact and follow-up process.
Import contacts with field checksValidate a small sample before importing a complete contact list.