Skip to main content
All CollectionsApps, Integrations & ImportIntegrations for Billing tools & Agency software
MOCO integration for transferring projects, times and absences
MOCO integration for transferring projects, times and absences
Johannes Kuhla avatar
Written by Johannes Kuhla
Updated this week

💡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:

General Information

The MOCO integration allows you to seamlessly transfer projects, time entries absences between awork and MOCO. This ensures that all important data is available in one place, supporting your workflows optimally. This article explains how to set up the integration and highlights its features.

Features of the MOCO Integration

Project Transfer:

  • New projects from MOCO can be created directly in awork.

  • It is possible to use project templates from awork.

  • Existing projects in awork can be transferred to MOCO.

Time Tracking:

  • Time entries tracked in awork are transferred automatically, eliminating the need for manual synchronization.

  • You can choose whether the transfer of times should only take place from a certain date onwards.

  • You can differentiate between billable and non-billable hours.

Absences:

  • Absences can be transferred from Moco to awork.

  • This applies to newly created or changed absences, not existing ones.

  • There is no synchronisation from awork to Moco when changes are made.

Functionality of the MOCO Interface

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

    • Start and end dates

    • Client (created or selected and assigned to the project).

  • The responsible project manager and project members are synchronised to awork.

2. Tasks from Service Items:

  • For each service item in the MOCO project, a task is created in the "MOCO" list in awork.

3. 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.

  • 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.

4. project creation in awork with templates:

  1. Create your own field: Create your own field in MOCO with the name “awork project template” as type “Single selection”.

  2. 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.

  3. Use template: The selected template is automatically used for project creation in awork.

Setting Up the MOCO Integration

1. Create an API Key in MOCO

  • Log in to your MOCO account and click the gear icon in the top-right corner.

  • Go to Extensions → API and Webhooks.

  • Scroll down and create a new API key:

    • Assign a name (e.g., "awork").

    • Select Full Access and set the validity period to Unlimited.

    • Copy the key and save 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)

    • Pay attention to case sensitivity.

    • Save both 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.

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.

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.

  • 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.

  • 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.

  • Resync Function:

    If a transfer fails and time entries need to be transferred to awork retroactively, please contact our support team. They can initiate a resync.

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

Is the title of the task in awork included in the description of the time tracking in Moco?

The task name is not transferred to the description of the time in Moco. Only the time tracking note is transferred from awork to the description of the Moco time entry.

Is the budget of projects and tasks created in Moco also transferred to awork?

The budget is not transferred from Mono to awork because a monetary budget is used in Moco, a time budget is used in awork.

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.

Are changes to the time trackings in awork also updated in Moco?

Yes, the duration and note of a time tracking are transferred to Moco when changes are made 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?

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?

No. Time trackings are only transferred from awork to Moco, not the other way round.

Are time trackings synchronised again from awork to Moco if the times have already been manually transferred to Moco and the integration is then activated?

Yes, the time trackings would be transferred again, but you can define a date from which they should be transferred.

Did this answer your question?