Open Integrations
Open My account → Integrations. Find the section for the platform you want to connect.
Connect your clients’ contact details to another platform or receive records from it. Check each destination and verify transfers before considering setup complete.
Choose the direction · Connect a CRM · Send to another platform · Receive clients · Review and disconnect
Distinguish sending contacts from receiving them.
Open My account → Integrations. Find the section for the platform you want to connect.
GoHighLevel, NinjaPipe and Send to another platform transfer contacts out of CoachPro Tools. Receive clients from another platform creates or updates records here. Zapier provides actions and events for configuring the direction.
Enter credentials and check the destination.
In the GoHighLevel section, enter the Location ID and that location’s private integration token. Select ? to read the panel instructions and check contact and location permissions in your provider.
Obtain credentials for the location you will use. Do not paste another account’s ID or a token from another location. Return to this section once you have both.
Select Connect. If a format error appears, correct the indicated field. If the server rejects the connection, check the location, token and permissions before retrying.
Check the name shown as connected. Review contacts sent, last transfer and pending items. The token is no longer displayed after connecting; check the destination name rather than the token.
Select Send all my clients to transfer existing records. Wait for the result and check a record in GoHighLevel. Later changes to records can generate further transfers.
Check the email and phone in Clients: GoHighLevel needs at least one. Save the correction and review the integration’s result and errors.
Enter the NinjaPipe API key, which starts with np_, and select Connect. Check confirmation. To transfer existing records, use the send-all-clients control in that section.
Check that you copied the full key without spaces or extra text. Read the message before connecting again.
Select Connect with Zapier. In Zapier, choose the CoachPro Tools event or action and complete the requested connection. To authorise incoming data in CoachPro Tools, create the key described below. Check the connected-Zaps indicator when you return.
Set up and test an outgoing address.
Under Send to another platform, enter a name identifying the destination and paste its HTTPS URL. Use the address that receives contacts in your automation.
The secret is optional. If your automation verifies the transfer signature, enter the same secret it uses for verification. If you have not configured that verification, leave the field empty.
Select Add address. Check that the destination appears in the list with the correct name and URL.
Read the message. Check that the address starts with https:// and contains no spaces. If the address limit is reached, review which destinations are still needed before removing one.
Select Test on the saved address. A test contact is sent so you can identify the fields. Check the CoachPro Tools message and receipt in your automation before using client data.
Select Send all on the correct row. Wait for processing and check sent, pending and error information. Check a received record; avoid repeating the full transfer only because it is not yet visible on another screen.
Create a key and configure incoming data.
Under Receive clients from another platform, select Copy beside the address. This URL is the destination for the action that creates or updates clients in CoachPro Tools.
Enter the automation or platform name and select Create key. Use a separate key to identify each connection.
Enter a name before creating it. The list later shows names and prefixes; a recognisable name helps you choose which connection to revoke.
Select Copy under Copy your key now and store it in your connection’s private settings. The full key is displayed once only. Do not include it in a public link.
The list does not let you recover the full key. Create a new one, update the connection and remove the old one once it is no longer used.
In your automation, use POST to the copied address and authorise with Authorization: Bearer KEY or X-API-Key: KEY. Send the contact fields name, email, phone, with at least an email or phone. Read the section’s ? instructions to check the format.
Test with a fictional contact and find the record in Clients. Check name, email and phone. An existing email updates its record; check the address before repeating a test on a real client.
Check errors before repeating a transfer.
Check the destination status: last transfer, pending items and any error message. Correct credentials, address or data according to the message and check receipt again. An active connection does not mean synchronisation is complete.
Use Disconnect for the CRM or Remove for an address and review confirmation. This stops future transfers to that destination; it does not delete contacts already received by the other platform.
Select Remove on the correct key and confirm after checking its name and prefix. The automation using it will no longer be authorised. When replacing it, configure and test the new key before removing the old one.
A visible connection does not prove that every contact arrived. Check the transfer result and the record in the destination platform.