The connection is made through OAuth 2.0. You start the process in Enginy, authorise access in TribeCRM, and come back to Enginy to finish the setup.
You do not need to copy an API key or type your organisation ID manually.
Before you start
Check that:
You can log in to the right TribeCRM environment.
Your user has permissions on the data Enginy will use.
Your browser allows pop-ups from Enginy.
There is no other active CRM.
You know which
Contact Type,Organization Typeand Task statuses you will use.
If you want to connect a sandbox, log in to that environment before you begin.
Connect TribeCRM
Open
Integrationsin Enginy.Go to
AllorDisabled.Find the TribeCRM card and turn on its switch.
In
Connect TribeCRM to Enginy, clickConnect to TribeCRM.If your browser blocks the window, allow pop-ups and try again.
Log in to TribeCRM and authorise Enginy.
TribeCRM supplies the organisation context automatically.
Go back to the Enginy tab to finish the setup.
Complete the initial setup
Open Sync Configuration and review these four values:
Contact TypeOrganization TypeDefault Task StatusCompleted Task Status
All four are required.
If a LinkedIn warning appears:
Click
Open Account Settings.Enable the LinkedIn module in TribeCRM.
Come back to Enginy.
Click
Recheck.
Then review Field Mapping, Campaign Mapping, User Mapping, and Tasks if it appears in your workspace.
Click Save Changes and confirm with Save.
Check the connection
The TribeCRM card should show the switch on and the Configure button.
Run a small test before processing lots of records:
Open
CRM Searchand clickFetchfor Contacts or Companies.Export a test Company.
Export a Contact associated with that Company.
Check the Relationship Type, the fields and the owner in TribeCRM.
If you use
Campaign Mapping, check an Activity too.
Reconnect TribeCRM
Enginy renews tokens automatically. You only need to reconnect when it can no longer renew access.
The card shows Reconnect when the authorisation has expired or stopped being valid.
Open
Integrations.Find TribeCRM.
Click
Reconnect.Log in to TribeCRM and authorise Enginy again.
Come back to Enginy.
Open
Configureand review the configuration.
If you want to connect with a different TribeCRM user, disconnect the current integration first and repeat the process with that user.
Disconnect TribeCRM from Enginy
Open
Integrations.Find TribeCRM.
Turn off the switch.
In
Disable TribeCRM, clickDisable.
When you disconnect:
Enginy deletes the stored credentials.
New imports and exports stop using TribeCRM.
Existing records are not deleted.
Activities and Tasks already created stay in TribeCRM.
The authorisation may still be active in TribeCRM until you revoke it there.
Important: Disconnecting in Enginy and revoking in TribeCRM are two different actions.
Revoke access in TribeCRM
To withdraw access completely:
Turn off TribeCRM from
Integrationsin Enginy.Go to the TribeCRM environment you authorised.
Open the settings for authorised apps or connections.
Find Enginy and revoke its access.
If you cannot manage apps, ask a TribeCRM administrator for help.
The exact location of this option can vary depending on your configuration and user permissions.
After revoking, you will need to start a new OAuth connection to use the integration again.
Common problems during connection
Problem | What to check |
TribeCRM does not open | Allow pop-ups and click |
Authorisation finishes, but it does not show as connected | Go back to the original tab and check you authorised the right environment |
| Check the user is still active and the app has not been revoked |
You cannot save | Fill in the four required TribeCRM fields |
Certain fields do not appear | Check permissions and the |
LinkedIn Activities are not logged | Enable the module and click |
Import works, but export fails | The user may have read access without create or edit permissions |
A new Contact is not created | Check that it has an associated Company |
