Start by reviewing the OAuth connection, the permissions of the user who authorised it, and the report from the last operation.
The connection has stopped working
Enginy uses OAuth 2.0 with read, write and offline.
offline lets it renew the access token automatically. Reconnect if:
The user revoked access.
The refresh token stopped being valid.
The user can no longer access the environment.
The account was deactivated.
A 401 error persists after the automatic refresh.
Disconnecting in Enginy deletes the local credentials, but it does not necessarily revoke access in TribeCRM. To withdraw it completely, also revoke the app from TribeCRM.
Error 401: Unauthorized
Enginy tries to renew the token automatically.
If the error persists:
Check the user is still active.
Check whether the app was revoked.
Click
Reconnect.Repeat only the operation that failed.
You do not need to renew the token manually.
Error 403: Forbidden
The connection is valid, but the OAuth user cannot perform the operation.
Review permissions on Persons, Organisations, Relationships, Activities, Tasks, and the custom fields in Field Mapping.
The user does not need to be an Administrator, but they do need to be able to read, create and modify everything Enginy uses.
User Mapping does not resolve a 403. Calls still use the original OAuth connection.
Error 429: Too Many Requests
TribeCRM documents 1,000 calls per minute per environment.
If you get a 429:
Wait at least a minute.
Check the report.
Find the affected records.
Retry only those records.
Avoid running several large operations at once.
Some records may have been processed before the limit was reached.
You cannot save the configuration
Check the four required fields: Contact Type, Organization Type, Default Task Status and Completed Task Status.
Click Save Changes and confirm with Save.
Fetch returns no records
Review:
The
Contact TypeorCompany Type.Read permissions.
That all the filters can be met at the same time.
That the fields belong to the chosen type.
That the Contact has a Relationship of that type.
That the Organisation has the selected type.
You can add up to five filters and they are all combined with AND.
If the Company fields do not change when you select another type, save Organization Type in Configure first and open the import again.
A new Contact is not exported
Usually an associated Organization is missing.
Associate the Contact with a Company.
Check the Company can be matched.
Export the Company if it does not exist yet.
Export the Contact again.
Review the report.
Duplicate Contacts were created
Standard matching compares first and last name. If Enginy knows the Organization's CRM ID, it also narrows the search to that relationship.
The Company name text does not replace the CRM ID.
Review the associated Company, the Organization's CRM ID, the LinkedIn URL, the Custom Mapping Conditions, and any incorrect CRM IDs stored in Enginy.
Duplicate Organizations were created
Website or company name does not run a prioritised search. Website and Name are alternatives within the same query.
Review Websites, duplicate Names and custom Conditions.
A field is missing after the export
A record can be created even if a field is not written.
Check:
The field is read-only.
The OAuth user can modify it.
The custom field still exists.
The type is compatible.
The Enumeration accepts the value.
The Enginy value is not empty.
The overwrite rule allows it to be changed.
The field belongs to the selected type.
A blue check does not guarantee that TribeCRM will accept any value.
An Enumeration does not show the value
TribeCRM only accepts options defined for the field.
If the value does not match, Enginy can skip that field and process the rest of the record. Check the exact name, capitalisation and spaces.
A conversation does not appear as an Activity
Check that:
The Contact has a CRM ID.
The Campaign allows exporting.
Campaign Mappingis saved.The OAuth user can create Activities.
Users and Identities are mapped.
The Activity type exists.
The API limit was not reached.
Emails use Activity_Email. LinkedIn, InMail and Connection messages use Activity_LinkedInMessage. They are not stored as Notes.
LinkedIn messages do not appear
The environment needs the LinkedIn module and Activity_LinkedInMessage.
Click Open Account Settings, enable the module and use Recheck.
A Task is not created
Review Default Task Status, Completed Task Status, the exact Task Type name, CRM Owner, User Mapping, OAuth permissions, and the Contact's CRM ID.
If the Tasks panel does not appear, the feature may not be enabled.
You deleted a Task, but it is still in TribeCRM
That is the expected behaviour.
Enginy marks it as closed through IsClosed and adds the closing date. It does not delete it.
You cannot find Lists, Leads or Notes
The import uses
CRM Search, not Lists.TribeCRM does not have a separate Lead object in this integration.
Conversations are stored as Activities, not as Notes.
Changes do not sync automatically
TribeCRM does not have continuous bi-sync in Enginy.
Sync with TribeCRM defines what happens during the next export. It does not watch every change in both systems.
Linked Tasks have a partial reverse update for some fields.
The process ended with partial results
Check the report.
Separate created, updated and failed records.
Fix each cause.
Retry only the affected ones.
Check the CRM IDs before another bulk process.
Asking for help
Include:
The type of operation.
The Enginy record ID or link.
The TribeCRM ID or link, if there is one.
The approximate time.
The error code.
The full message from the report.
The object and field affected.
The user who authorised OAuth.
A screenshot of the related configuration.