MOCO integration for transferring projects, time entries, and absences

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

MOCO is agency software that helps you manage your accounting without stress or paperwork, along with many other useful features.

We offer several integrations for MOCO:

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, so you can track time directly in MOCO while working in awork

---

General information

The MOCO integration is a paid add-on that enables seamless transfer of projects, time entries, and absences between awork and MOCO. This keeps all relevant data in one place and helps you work more efficiently. This article explains how to set up the integration and what it can do for you.

---

What features does the integration offer?

Projects

• Sync new projects from MOCO to awork
• Use project templates from awork
• Link existing awork projects to a MOCO project

Time tracking

• Automatically transfer all time entries recorded on linked projects.
  (Time entries without a project, such as those recorded with a global timer, as well as time entries before the configured start date, are skipped.)
• Option to start transferring time entries from a specific date
• Option to distinguish between billable and non-billable time

Absences

• New, edited, and deleted absences are transferred from MOCO to awork.
• Existing absences from the previous day onward are transferred within one day of activation.
• The Support Team can transfer older absences retroactively upon request.
• The type of absence, such as vacation or sick leave, is not transferred.
• No sync in the other direction (awork → MOCO)

---

How does the integration work technically?

1. Creating a project:

• Create the project in MOCO and select the Sync zu awork checkbox in the custom field.
• The integration automatically creates the project in awork. The following data is transferred:
  • Project number
  • Project name
  • Start and end dates
  • Client (created or selected, then assigned to the project).
• By default, the project owner and project members are synced to awork.
  • The project lead in MOCO is added as the responsible member. Co-project leads and people scheduled to track time are added as members.
  • Members are only added, never removed.
  • Only users who can be matched by email address are added.
  • Members are no longer changed for archived or inactive MOCO projects.

2. Tasks from service items:

Depending on the selected mode (see Time tracking modes: task lists vs. tasks), either a task is created for each service item in the MOCO project in the "MOCO" list in awork, or a task list is created.

3. Time tracking:

• A time entry is created in awork on the linked project.
  • If the time was tracked on a task created from a MOCO service item, it is assigned directly.
  • If a direct assignment is not possible, the time entry is matched based on the activity name and the MOCO item name.
  • If no match is found, a new "Unassigned" service item is created in MOCO and the time is assigned to it.
  • Subtasks are assigned to the same MOCO service item as the parent task.
• Users in MOCO and awork are matched by email address. The integration first checks the Workspace Email and, if it is not set, the Account Email (used to log in). Only active users who are not external users are matched.
• Information about whether the time is billable or non-billable is transferred.
• You can edit or delete time entries in awork after they have been recorded. These changes are also transferred to MOCO.

---

Time tracking modes: task lists vs. tasks

There are two supported modes for syncing time tracking between MOCO and awork:

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

Each mode determines how service items and tracked time are matched between the systems.

1. Time tracking via task lists (recommended)

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

• Reusing existing task lists: If the project template already contains task lists with identical names, those lists are reused and tasks are assigned to the matching existing lists instead of creating duplicates.
• Assigning time entries: All time tracked within the corresponding task list is assigned to the linked service item, including time tracked on tasks and subtasks.
• Matching logic: MOCO service item = awork task list. Time tracked on tasks or subtasks = assigned to the corresponding service item.

2. Time tracking via tasks

A list named "MOCO" is created automatically in awork. A separate task is created in this list for each MOCO service item.

• Assigning time entries: Time tracked directly on these generated tasks is synced back to the corresponding service item. The assignment is made directly through the task created from the service item or through the linked awork activity.
• Matching logic: MOCO service item = task in the "MOCO" list in awork. Time tracked on a task or activity = transferred to the corresponding service item.

---

Custom fields in MOCO

To ensure that data is transferred correctly, these three custom fields are set up automatically in MOCO when the Moco integration is activated:

• awork Projekt (Type: Link)
• Sync zu awork (Type: Yes/No)
• awork Projektvorlage (Type: Single select)

---

How do I set up the integration?

Step 1: Create an API key in MOCO

• In your MOCO account, go to Einstellungen (gear icon in the top right) → Erweiterungen → API und Webhooks
• Create a new API key with:
  • A name (e.g. "awork")
  • Vollzugriff, unlimitiert gültig
  • Copy the key and store it somewhere safe

Step 2: Activate the integration in awork

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

Send them the key you just created and your MOCO subdomain using a secure method. awork needs both details to configure the interface.

Step 3: Run an initial test

1. Create a project:

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

2. Check the transfer:

• Check in awork whether the project was transferred correctly.

---

Additional optional integration settings

The following optional settings can be configured:

Please let us know which options you want us to enable for your workspace.

---

Creating projects in awork from templates (optional)

1. Open the custom field in Moco: In MOCO, open Einstellungen (gear icon in the top right) and select the custom field named awork Projektvorlage.
2. Add templates: Add the templates you want to use in MOCO/awork to the single-select options. Important: Make sure there are no spaces before or after the commas.
3. Use a template: The selected template will be used automatically when creating a awork Projekt 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 relevant projects. These settings must be identical in awork and MOCO. In MOCO, the user needs full access to projects and must be added to the project as a "Person für die Zeiterfassung".
• Send existing MOCO projects to awork: To create existing MOCO projects in awork, simply enable Sync zu awork for them. The awork Projekt will then be created in awork.
• Transfer existing awork projects to MOCO:
  To transfer existing awork projects to MOCO, create a MOCO project, add the corresponding awork Projekt link, and then enable Sync zu awork.
• Changing your custom subdomain: If you change your awork domain, the integration will continue to work without any changes. The awork links in MOCO will be updated automatically the next time you save the relevant awork Projekt.
• Deleted services in Moco: If a service is deleted in MOCO and a service with the same name already exists in the same awork Projekt or is created later, awork will automatically assign the corresponding task or task list to that service.

Troubleshooting with the awork Agent

Use the awork Agent (🔐 available on the Standard plan) to investigate any sync issues.

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

• Find out why syncs failed or were skipped: It explains why a sync failed or was skipped.

• Resync individual projects and time entries, all time entries for a specific period or awork Projekt, or absences

• Confirm before running: The Agent will ask you to confirm before resyncing.

• Example requests: Why did my MOCO sync fail? Resync this time entry. Why didn't this awork Projekt sync? Check the execution log and resync this awork Projekt.

---

Canceling the MOCO integration

You can't cancel the MOCO integration yourself in awork. Contact our Support team at support@awork.com.

---

Frequently asked questions (FAQ)

How much does the integration cost?

The integration costs a flat fee of €50 per month. The minimum contract term and cancellation period for this add-on depend on the terms of your current plan.

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

Yes, the task name can be copied to the notes field of the time entry in MOCO. Just let the Support team know when you activate the integration that you want to use this feature. It can also be enabled later.

Can I rename a task in awork without affecting time tracking?

Time tracking will still be assigned correctly even if you rename a task.

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

Yes, changes to the duration, note, date, billability, task, task list, and awork Projekt of a time entry are synced. Changing the task or task list also changes the associated service item.

Will time entries be synced from awork to MOCO again if they were already transferred to MOCO manually before the integration was activated?

Yes, the time entries will be transferred again. However, you can specify a date from which time entries should be transferred. Let our Support Team know this date when the integration is activated.

Can changes to projects in MOCO be synced to awork after the awork Projekt has been created?

Yes. Changes to a linked MOCO awork Projekt are automatically transferred to awork: the awork Projekt name, client, start and end dates, and description. New and updated services are transferred as well. awork Projekt members are only updated when changes are made.

Prerequisite: Updating awork Projekt data and awork Projekt members must be enabled in the configuration. Either can be disabled by our Support Team upon request.

Are time entries edited or deleted in MOCO also edited or deleted in awork?

If a time entry is edited or deleted in MOCO, the change is not synced to awork. However, if you edit or delete a time entry in awork, it will also be updated or deleted in MOCO.

If a awork Projekt is deleted in MOCO, is the awork Projekt in awork deleted too?

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

Can time entries be synced from MOCO to awork?

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

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

The budget is not transferred directly from MOCO to awork. MOCO uses a monetary budget, while awork uses a time-based budget. The planned effort for a task or task list is calculated from the MOCO service budget and hourly rate (formula: MOCO budget / MOCO hourly rate = awork planned effort). If the hourly rate is set per awork Projekt, the awork Projekt hourly rate is used. If it is set per service, the service hourly rate is used. No planned effort is set for hourly rates defined per person or for services without a budget.

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

Yes. In Time tracking via tasks mode, the description of the MOCO service is added when the awork task is created. Later changes are not transferred. In Time tracking via task lists mode, the description cannot be transferred.

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 completely, including when new projects are created. Please contact Support so we can configure the integration accordingly.

I already created a project in MOCO, and it was transferred to awork. Can I create a new awork Projekt from this project?

First, delete the existing awork Projekt, or ask Support to link the MOCO project to a new awork Projekt. Then replace the awork link in the MOCO project with https://recreate and save it. If a new project does not appear in awork, save the MOCO project again or wait until the next day.

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

Not yourself. An awork Projekt can only be linked to one MOCO project. If a link needs to be changed, Support can take care of it.

Who is responsible for the MOCO integration?

awork is responsible for the integration. If you have any questions, contact the awork Support Team.