💡The integration is subject to a fee. If you would like to use our MOCO integration, contact us at [email protected]. We are looking forward to hearing from you.
MOCO is an agency software that lets you do your accounting besides many other things without chaos and paperwork.
For MOCO we have different integrations:
Chargeable MOCO integration for transferring projects and times
General Information
The MOCO integration is a paid add-on module that enables seamless transfer of projects, time tracking entries, and absences between awork and MOCO. This ensures that all relevant data is centrally available and supports your workflow efficiently.
Which Features does the MOCO Integration offer?
Projects
Synchronisation of new projects from MOCO to awork
Use of project templates from awork
Transfer of existing projects from awork to MOCO
Time tracking
Automatic transfer of all times, no manual rework required
Option to start the transfer only from a specific point in time
Distinction between billable and non-billable times possible
Absences
Only new or changed absences are synchronised from MOCO to awork
No synchronisation in the other direction (awork → MOCO)
How does the MOCO Integration work?
1. Project Creation:
The project is newly created in MOCO and tagged with "Sync to awork."
The interface automatically creates the project in awork, transferring the following data:
Project number
Project name
Deadline
Client (created or selected and assigned to the project).
The responsible project manager and project members are synchronised to awork by default.
2. Time Tracking:
A time entry is created in awork for the linked project.
If the time was logged on a task that originated from a MOCO service item, the time is directly assigned to it.
If no direct assignment is possible, the time entry is matched based on the activity name and the name of the MOCO service item.
If no match is found, a new service item named "Unassigned Time Entry" is created in MOCO, and the time is assigned there.
Sub tasks are assigned to the same MOCO service item as the main task.
Users in MOCO and awork are matched via their email addresses.
Important: The email address must be stored as a work email in Account settings (After click on the profile picture on the top right hand side) > Edit user > Contact information. Admins can adjust this email address for other under Users in the left hand navigation bar.Information about whether the time is billable or non-billable is also transferred.
Time entries can be modified or deleted in awork afterward, and these changes are also reflected in MOCO.
Project creation in awork with templates
Create your own field: Create your own field in MOCO with the name “awork project template” as type “Single selection”.
Add templates: Add the templates you want to use in MOCO/awork to the single selection options. Important: Make sure that there are no spaces before or after the comma.
Use template: The selected template is automatically used for project creation in awork.
If you want no template to be selected by default, or if users should be able to create a project completely without a template, then you need to place a comma at the beginning.
Time Tracking Modes: Task Lists vs. Tasks
There are two supported modes for synchronizing time tracking between MOCO and awork:
Time Tracking via Task Lists (recommended)
Time Tracking via Tasks
Each mode determines how service items and tracked times are mapped between systems.
1. Time Tracking via Task Lists
A separate task list is created in awork for each service item. No tasks are created automatically. Users can manually create tasks or subtasks inside the generated task lists.
Existing Task List Matching: If the project template already contains task lists with identical names: The existing task lists are reused and tasks are assigned to the existing matching lists instead of creating duplicates.
Time Tracking Assignment: Any time tracked within the corresponding task list is assigned to the linked service item, including time tracked on tasks and time tracked on subtasks.
Mapping Logic: Moco Service Item = Task List in awork. Tracked time on tasks/subtasks = Assigned back to the corresponding service item.
This mode is recommended because it provides:
More flexibility in task organization
Better compatibility with project templates
Cleaner project structures
Easier manual task management
2. Time Tracking via Tasks
A task list named "MOCO" is automatically created in awork. A separate task is created inside this list for each MOCO service item.
Time Tracking Assignment: Time tracked directly on these generated tasks is transferred back to the corresponding service item. Any time tracked on the task is assigned to the linked service item in Moco. Or via the linked awork activity.
Mapping Logic: Moco Service Item = Task inside "MOCO" list in awork. Tracked time on task or activity = Transferred back to corresponding service item.
How do I set up the MOCO Integration
1. Create an API Key in MOCO
In the MOCO account: Gear icon → Extensions → API and Webhooks
Create a new API key with:
Name (e.g., “awork”)
Full access, unlimited validity
Copy the key and store it securely
2. Create Custom Fields in MOCO
To ensure proper data transfer, you need to create custom fields in MOCO:
Navigate to Settings → Custom Fields.
Create the following fields:
awork Projekt (Type: Link)
Sync zu awork (Type: Yes/No)
awork Projektvorlage (Type: Single selection). Add template names as described above.
While creating the custom fields choose Project from the dropdown in the second row.
Pay attention to case sensitivity.
Save fields.
3. Enable the Integration in awork
Contact our support team to request activation of the MOCO interface for your awork workspace.
Provide the API key and your MOCO subdomain. Both are required to configure the integration.
Please let the team know how the following features should be configured:
Sync of absences from MOCO to awork: Yes/No
Timetracking via Tasklists or via Tasks
Should the time tracking be transferred from a certain point of time?
4. Initial Test
Create a Project:
Create a new project in MOCO and activate the Sync zu awork field.
Save the project.
Verify Transfer:
Check in awork to ensure the project has been transferred correctly.
Additional optional integration settings
The following optional settings can be configured:
Ignore unplannable absences: choose whether you want to skip the sync of unplannable MOCO absences
Disable MOCO-driven awork project data update: prevents MOCO project changes from overwriting awork project data (includes project budget and project description)
or only disable updates of awork project descriptions: allows project data updates while preserving existing awork project descriptions to avoid text overwrites
Remove MOCO ID prefix in awork project names for cleaner naming standards per workspace ("Project Name" instead of "P1234 - Project Name")
Update project budget from planned durations: calculates the awork project budget from the total planned durations of tasks and task lists
Disable staffing update on project update
or never update staffing: completely disables staffing synchronization between MOCO and awork
Please let us know which options should be enabled for your workspace.
Important Notes
User Permissions in Both Systems:
Ensure that user permissions are correctly configured in both systems and that the users are assigned to the relevant projects in both awork and MOCO. The user needs full access to projects in MOCO and must be added to the project as a “person for time tracking.”Existing MOCO projects:
If you want to create existing MOCO projects in awork, simply activate the "Sync zu awork". The project will then be created in awork.Own subdomain:
If you change your awork domain after the MOCO integration was activated, please contact our support team, as the domain needs to be updated for the integration.
Existing awork projects:
To transfer existing awork projects to MOCO, create a MOCO project, add the corresponding awork project link, and activate the "Sync zu awork" field afterwards.
Projects can only be linked once. awork project links that have already been used cannot be inserted into another Moco project. This will lead to errors during synchronisation.
Cancellation of the MOCO integration
The MOCO integration cannot be canceled by the user in awork. To do so, please contact our support team at [email protected]
Frequently Asked Questions
How much does the integration cost?
How much does the integration cost?
For the integration, we charge a fixed price of 50 EUR per month. The minimum contract duration and notice period for this add-on depend on the conditions of your current plan.
Is the title of the task in awork included in the description of the time tracking in MOCO?
Is the title of the task in awork included in the description of the time tracking in MOCO?
Yes, the task name can be transferred to the notes field of the time tracking in MOCO. Just let the support team know that you would like to use this feature when the integration gets activated. The feature can also be activated retroactively.
Can a task be renamed in awork or will time trackings then no longer be assigned?
Can a task be renamed in awork or will time trackings then no longer be assigned?
The allocation of time trackings continues to work, even if a task is renamed in awork.
Are changes to the time trackings in awork in awork also updated in MOCO?
Are changes to the time trackings in awork in awork also updated in MOCO?
Yes, the duration and note of a time tracking is transferred to MOCO when changes are made in awork.
If time tracking entries are already manually created in MOCO, will they be transferred again from awork?
If time tracking entries are already manually created in MOCO, will they be transferred again from awork?
Yes, the time trackings would be transferred again, but you can define a date from which they should be transferred. Please inform our support team of this when activating the integration.
Can changes made to a MOCO project after its initial creation be transferred to awork?”
Can changes made to a MOCO project after its initial creation be transferred to awork?”
Only new services and projects members can be synced to awork after the project has been created in MOCO. To trigger a sync, the project name needs to be adjusted (e.g. by adding a space to the end).
Are time trackings that are edited/deleted in MOCO also edited/deleted in awork?
Are time trackings that are edited/deleted in MOCO also edited/deleted in awork?
If a time tracking is edited or deleted in MOCO, there is no synchronisation to awork. If you change or delete a time tracking in awork, it will also be updated or deleted in MOCO.
If a project is deleted in MOCO, is the project also deleted in awork?
If a project is deleted in MOCO, is the project also deleted in awork?
No, deleting a project in MOCO has no effect on the project in awork. The project in awork is not deleted as a result.
Can time trackings be synchronised from MOCO to awork?
Can time trackings be synchronised from MOCO to awork?
No. Time trackings are only transferred from awork to MOCO, not the other way round.
Is the budget of tasks created in MOCO also transferred to awork?
Is the budget of tasks created in MOCO also transferred to awork?
The budget is not transferred directly from MOCO to awork. A monetary budget is used in MOCO and a time-based budget in awork. However, the planned effort of a task in awork is based on the budget of a MOCO service and the hourly rate stored in MOCO. (Formula: MOCO budget / MOCO hourly rate = awork planned effort)
If there is no budget set for a service, the integration instead uses the budget set for the project in MOCO.
Is the description of a service item from MOCO transferred to the description field in awork?
Is the description of a service item from MOCO transferred to the description field in awork?
Yes, that is possible. The description can be transferred here as well.
Can the transfer of project members from MOCO to awork be deactivated?
Can the transfer of project members from MOCO to awork be deactivated?
Yes, the transfer of project members can either be deactivated for existing projects or for creating new projects as well. Please reach out to our support team so we can configure the integration accordingly.
I have created a project in MOCO which has been synced to awork. Can I create another awork project from the same one in MOCO?
I have created a project in MOCO which has been synced to awork. Can I create another awork project from the same one in MOCO?
The projects are automatically linked. If you want to delete the link, you can remove the checkbox for "Sync zu awork".
If you want to create a new awork project from the project in MOCO, follow these steps:
Edit the MOCO project and delete the awork link
Im URL field, paste the following text: https://recreate
Once you save this in MOCO, a new project will be generated in awork
Can I change the linking later and link an awork project to another Moco project?
Can I change the linking later and link an awork project to another Moco project?
No, an awork project can only be linked to one Moco project. If, for example, a Moco project is being archived, the awork project cannot be linked to another Moco project. The original connection stays active.