MOCO Integration for Transferring Projects, Time Entries, and Absences

💡 This interface is a paid add-on. If you'd like to use our MOCO integration, just get in touch with us at sales@awork.com. We look forward to hearing from you!

MOCO is agency software that lets you handle your accounting along with many other helpful features without stress and paperwork.

For MOCO, we offer several integrations:

1. Free MOCO integration for invoices
2. Paid MOCO integration for transferring projects and time entries
3. Free MOCO browser extension for Chrome and Firefox to log time directly in MOCO while you work in awork

---

General Information

The MOCO integration is a paid add-on module that enables seamless transfer of projects, time entries, and absences between awork and MOCO. This keeps all relevant data centrally available and supports your workflow efficiently. In this article, you'll learn how to set up the integration and what features it offers.

---

What features does the integration provide?

Projects

• Synchronization of new projects from MOCO to awork
• Using project templates from awork
• Transfer of existing projects from awork to MOCO

Time Entries

• Automatic transfer of all time entries - no manual follow-up needed
• Option to start the transfer from a specific point in time
• Ability to distinguish between billable and non-billable time

Absences

• Only new or modified absences are synchronized from MOCO to awork
• No synchronization in the other direction (awork to MOCO)

---

How does the integration work technically?

1. Project Creation:

• The project is created in MOCO and tagged with "Sync to awork".
• The interface automatically creates the project in awork. The following data is transferred:
  • Project number
  • Project name
  • Start and end date
  • Client (will be created or selected and assigned to the project)
• Project manager and project members are synchronized to awork by default.

2. Tasks from Service Positions:

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

3. Time Entry:

• A time entry is created in awork on the linked project.
  • If the time was logged on a task created from a MOCO service position, the time is assigned directly.
  • If direct assignment isn't possible, the time entry is matched based on the activity name and the MOCO position name.
  • If no match is found, a new service position called "Unassigned Time Entry" is created in MOCO and the time is assigned there.
  • Subtasks are assigned to the same MOCO service position as the main task.
• The user from MOCO and awork is matched via email address.
  Important: The email address in awork must be saved as a business email under Account Settings (click your profile picture in the top right) > Edit User > Contact. Admins can also adjust the email for other users under Users in the left navigation bar.
• Information about whether the time is billable or non-billable is transferred.
• Times can be edited or deleted in awork afterwards. These adjustments are also transferred to MOCO.

---

Time Entry Modes: Task Lists vs. Tasks

For synchronizing time entries between MOCO and awork, there are two supported modes:

1. Time entry via task lists (recommended)
2. Time entry via tasks

Each mode determines how service positions and logged time are matched between the systems.

1. Time Entry via Task Lists (Recommended)

A separate task list is created in awork for each service position. Tasks are not created automatically. Users can manually create tasks or subtasks within the generated task lists.

• Reusing existing task lists: If the project template already contains task lists with identical names, these existing task lists are reused and tasks are assigned to the matching existing lists instead of creating duplicates.
• Time entry assignment: All times logged within the corresponding task list are assigned to the linked service position, including times on tasks and subtasks.
• Assignment logic: MOCO service position = task list in awork. Logged times on tasks/subtasks = assignment to the corresponding service position.

2. Time Entry via Tasks

A list named "MOCO" is automatically created in awork. Within this list, a separate task is created for each MOCO service position.

• Time entry assignment: Times logged directly on these created tasks are synchronized back to the corresponding service position. Assignment happens either directly via the task created from the service position or via the linked awork activity.
• Assignment logic: MOCO service position = task within the "MOCO" list in awork. Logged time on task or activity = transfer to the corresponding service position.

---

How do I set up the integration?

Step 1: Create API Key in MOCO

• In your MOCO account: Settings (gear icon in top right) → Extensions → API and Webhooks
• Create a new API key with:
  • Name (e.g., "awork")
  • Full access, unlimited validity
  • Copy the key and keep it safe

2. Create Custom Fields in MOCO

To ensure proper transfer, custom fields must be set up in MOCO:

1. Go to Settings (gear icon in top right) → Custom Fields.
2. Create the following fields:

• awork Project (Type: Link)
• Sync to awork (Type: Yes/No)
• awork Project Template (Type: Single Select). Add template names as described above.

3. When creating, select Project in the second row for each field.
4. Pay attention to capitalization.
5. Save the fields.

3. Activate Integration in awork

Now contact our support team and ask them to enable the MOCO interface in awork for you.

Send the newly created key and your MOCO subdomain via a secure channel. awork needs both to configure the interface.

4. First Test

1. Create a project:

• Create a new project in MOCO and enable the Sync to awork field.
• Save the project.

2. Check the transfer:

• Verify in awork that the project was transferred correctly.

---

Additional Optional Integration Settings

The following optional settings can be configured:

Please let us know which options you'd like us to enable for your workspace.

---

Project Creation in awork with Templates

1. Create a custom field: In MOCO settings (gear icon in top right), create a custom field called "awork Project Template" as type "Single Select".
2. Add templates: Add to the single select options the templates you want to use in MOCO/awork. Important: Make sure there are no spaces before or after the comma.
3. Use the template: The selected template will automatically be used for project creation in awork.

---

Important Notes and Troubleshooting

• User permissions in both systems:
  Check that user permissions are set correctly in both systems and that the user is assigned to the respective projects. This must be identical in awork and MOCO. In MOCO, the user needs full access to projects and must be added as "Person for Time Tracking" to the project.
• Transfer existing MOCO projects to awork: If you want to create existing MOCO projects in awork, simply enable Sync to awork afterwards. The project will then be created in awork.
• Your own subdomain: If you change your awork domain after activating the MOCO integration, please contact support so the domain can be updated for the integration.
• Transfer existing awork projects to MOCO:
  If you want to transfer existing awork projects to MOCO afterwards, create a MOCO project, add the corresponding awork project link, and then enable Sync to awork.

Troubleshooting with the awork Agent

Use the awork Agent (🔐 from the Standard Plan onwards) to analyze potential synchronization issues.

• Check execution logs: The awork Agent analyzes the available MOCO logs.

• Explain failed or skipped synchronizations: It shows you why a synchronization failed or was skipped.

• Synchronize individual time entries or projects: You can specifically resynchronize a time entry or a project.

• Confirm before execution: The Agent asks for your confirmation before a resync.

• Example queries: Why did my MOCO synchronization fail? Resync this time entry. Why wasn't this project synchronized? Check the execution log and resync this project.

---

Canceling the MOCO Integration

The MOCO integration cannot be canceled by users themselves in awork. Please contact our support team at support@awork.com.

---

Frequently Asked Questions (FAQ)

What does the integration cost?

We charge a fixed price of 50 euros per month for the integration. The minimum contract duration and notice period for this add-on are governed by the terms of your current plan.

Is the task title in awork transferred to the description of the time entry in MOCO?

Yes, the task name can be transferred to the notes field of the time entry in MOCO. Just let our support team know when activating the integration if you'd like to use this feature. The feature can also be enabled afterwards.

Can a task in awork be renamed, or will times no longer be assigned afterwards?

Time entry assignment will continue to work even if a task is renamed.

Are changes to time entries in awork also updated in MOCO?

Yes, duration and notes of a time entry are transferred to MOCO when changes are made in awork.

Will times be resynchronized from awork to MOCO if times were already manually transferred to MOCO and the integration is activated afterwards?

Yes, the times would be transferred again. However, you can define a point in time from which the transfer of times should occur. Inform our support team of this point in time when the interface is activated.

Is it possible for changes to projects in MOCO to also be synchronized to awork after the initial project creation?

Resynchronization only occurs for newly created services and the project members specified in MOCO. To trigger synchronization, the project name must be edited (for example, by adding a space at the end).

If times are edited or deleted in MOCO, are they also edited or deleted in awork?

If a time entry is edited or deleted in MOCO, no synchronization to awork occurs. Conversely, if you edit or delete a time entry in awork, it will also be updated or deleted in MOCO.

If a project is deleted in MOCO, is the project in awork also deleted?

No, deleting a project in MOCO has no effect on the project in awork. The project in awork will not be deleted.

Can time entries be synchronized from MOCO to awork?

Time entries are only transferred from awork to MOCO, not the other way around.

Is the budget of tasks created in MOCO also transferred to awork?

The budget is not directly transferred from MOCO to awork. MOCO uses a monetary budget, while awork uses a time-based budget. However, the planned effort of a task in awork is based on the budget of a MOCO service and the hourly rate saved in MOCO. (Formula: MOCO Budget / MOCO Hourly Rate = awork Planned Effort)

If no budget is saved for the service, the integration uses the budget of the MOCO project.

Is the description of the service from MOCO transferred to the description field in awork?

Yes, that's possible. The description should be transferred here.

Can the transfer of project members from MOCO to awork be disabled?

Yes, the transfer of project members can be disabled either only for existing projects or also when creating new projects. Please contact support so we can configure the interface accordingly.

I already created a project in MOCO that was transferred to awork. Can I create a new awork project from this project?

The projects are automatically linked. If you want to delete the link, you can disable the Sync checkbox in MOCO.

If you want to create a new awork project from the MOCO project, proceed as follows:

• Edit the project in MOCO and delete the awork link
• In the link field, add the following text: https://recreate
• Once you save the project in MOCO, a new project will be created in awork

Can I change the link later and link an awork project with a different MOCO project?

No, an awork project can only be linked with one MOCO project. If, for example, a MOCO project is archived, the awork project cannot be linked with another MOCO project. The original link remains.

Who is responsible for the MOCO integration?

awork is responsible for the integration. Contact the awork support team with any questions.