Enginy can create, update and close Tasks in TribeCRM.
The sync applies to Tasks that Enginy manages. It does not cover every Task that already exists in TribeCRM.
Required configuration
The four TribeCRM values are mandatory:
Contact TypeOrganization TypeDefault Task StatusCompleted Task Status
To use Tasks you also need:
A valid
Task Type.A
CRM Owner.A match in
User Mapping.Permissions to create and modify Tasks.
Access to the
Taskspanel in your workspace.
If the panel does not appear, the feature may not be enabled. The four Sync Configuration values are still required.
Configure statuses
Open TribeCRM from
Integrationsand clickConfigure.Go to
Sync Configuration.Select
Default Task Status.Select
Completed Task Status.Click
Save Changes.
Both statuses have to exist in the connected environment.
Configure Task Types
Go to
Tasks.Match the Enginy types with the TribeCRM types.
Check that the name matches exactly.
Save the changes.
Test with a single Task.
If the name does not match, Enginy cannot find the type and the Task is not created.
Configure owners
In User Mapping, match the Enginy user with the TribeCRM user.
The owner is stored as Assignee. A Task without a valid CRM Owner may not sync.
Permissions still come from the OAuth user.
Data sent to TribeCRM
Enginy can send:
Subject.
Due date.
Description or notes.
Priority.
Assignee.
Open or completed status.
A new Task uses Default Task Status. When you complete it, Enginy applies Completed Task Status, sets IsClosed and records the closing date.
If the Contact does not exist yet
Enginy tries to export the linked Contact first.
To create that new Contact, it needs an associated Company. If the Contact export fails, the Task may not be created.
Changes pulled back from TribeCRM
For Tasks that are already linked, Enginy can pull back:
Subject.
Due date.
Assignee.
Closed status through
IsClosed.
The pull-back is partial. It does not automatically update Description or Task Type, and it does not discover new Tasks created directly in TribeCRM.
Deleting a Task
Deleting a Task in Enginy does not delete it from TribeCRM.
Enginy marks it as closed and adds the closing date, so the history is preserved.
Tasks created by Sequences
A Sequence can create a Task when:
The Contact is linked.
The Task Type exists.
The owner has a match.
Both statuses are configured.
The OAuth user has permissions.
If a Task does not sync
Check that the
Taskspanel is available.Review
Default Task StatusandCompleted Task Status.Confirm the exact
Task Typename.Assign a
CRM Owner.Review
User Mapping.Check the OAuth permissions.
Confirm the Contact has a CRM ID or can be exported.
Check whether TribeCRM returned a 429.
Fix the configuration and test with a single Task.