Skip to main content

QuoJob Integration

Sync jobs, offers, time entries, and absences between QuoJob and awork to manage planning and billing in one workflow without duplicating data

Sync jobs, tasks, time entries, and absences between Fortes QuoJob and awork to avoid maintaining the same data twice.


Key benefits and use cases

The QuoJob integration connects your planning and work in awork with your billing in QuoJob.

  • Jobs become projects: Every QuoJob job you mark for syncing becomes an awork project. Its commissioned offers become task lists and tasks. Each project links to its job and uses the job number as its project key.

  • Time entries sync back: Time entries recorded in awork are created, updated, or deleted as hour bookings on the corresponding QuoJob job and service type.

  • Absences sync over: Approved vacation and sick leave can be imported from QuoJob as awork absences.

This way, your team avoids maintaining project data twice and can work with the information it needs in each tool.


How the QuoJob integration works

QuoJob sends the plan to awork, and awork sends time entries back.

Three data flows run each time QuoJob is checked. Time entries flow in the other direction as soon as someone saves them.

  • QuoJob → awork: Jobs, offers, and optionally vacation and sick leave are transferred regularly.

  • awork → QuoJob: Saved, updated, or deleted time entries are transferred immediately.

  • Linking: The awork project contains a link to the QuoJob job. QuoJob receives a link to the awork project.


What you need to set up the integration

Prepare the following in QuoJob before setting up the integration.

RequirementWhat it's forResponsible
Your QuoJob addressThe URL of your QuoJob installation, for example https://quojob.example.com/q40_pm.You
A technical QuoJob userawork reads and writes QuoJob data using this user. It needs read access to jobs, offers, employees, service types, vacation, and sick leave; permission to view sales prices (awork uses these to read the components of a composite service); and permission to book hours for other employees.Your QuoJob administrator
An application keyQuoJob only allows API access with a key issued by QuoTec.QuoTec
Checkbox attribute Sync zu awork on the jobSelect it for every job you want to appear in awork.Your QuoJob administrator
Text attribute awork Projekt on the jobawork adds the link to the awork project here, so you can jump straight from the job to awork.Your QuoJob administrator
Matching email addressesawork matches people by email address: the internal email address in QuoJob must match the work email address in awork.Your QuoJob and awork administrators
A fallback user (optional)A QuoJob user to whom awork books time entries for people who don't have their own QuoJob user, such as freelancers who are external users in awork. This user needs permission to book hours on all synced jobs.Your QuoJob administrator
Templates for each job type (optional)An awork project template with exactly the same name as a QuoJob job type is used for new projects of that type.Your awork administrator

You can give the two attributes different names. If you do, let us know what they're called. awork can't create attributes in QuoJob, so they must already exist before setup.


How to set up the integration

awork Support will connect QuoJob for you.

  1. Prepare all the requirements listed in What you need to set up the integration.
  2. Choose the integration options you want.
  3. In awork, open Einstellungen (the gear icon in the bottom left of the main menu) > Integrationen. Click Integrations-Bibliothek öffnen and select QuoJob in the Agentursoftware section.
    Click Support kontaktieren to open the chat window and contact awork Support directly. Alternatively, email support@awork.com.
  4. Share your QuoJob address, the username and password for the technical user, the application key, and your options with Support. Use a secure channel for this, never a regular email.
  5. awork checks the connection, login, and whether both attributes exist. If you use a fallback user, awork also checks that exactly one active QuoJob user has that email address.
  6. Select Sync zu awork on a test job.
  7. After the next sync interval, check whether the project appears in awork and whether awork Projekt contains the project link.
  8. Record a short time entry on a task in this project and check the hour booking in QuoJob.
  9. If everything looks good, select Sync zu awork for the remaining jobs.

Which options can you choose?

OptionDefaultWhat it does
Sync interval5 minutesHow often awork checks QuoJob for changes. You can choose an interval from 1 minute to 24 hours.
Default project templateNoneA new project uses the awork template with the same name as its job type. If there is no matching template, it uses this default template.
SubjobsSeparate projectEach subjob gets its own awork project. Or you can combine subjobs in the project of their parent job. See Good to know.
AbsencesOffImports approved vacation and sick leave from QuoJob as awork absences.
Start date for time entriesNoneTime entries before this date are never booked in QuoJob. This keeps old awork time entries from being added to QuoJob.
Task name in booking textOffThe hour booking text starts with the task name, followed by the time entry note.
Fallback userOffThe email address of a QuoJob user. awork books time entries for people without a QuoJob user to this user, and the booking text starts with the person's name, for example [Erika Musterfrau] Kickoff.

Decide on the subjob option before the first sync. Any later change only applies to subjobs that haven't been synced yet. Subjobs that have already been synced, along with their tasks and time entries, stay where they are.


What gets synced

QuoJob sends the plan to awork. awork sends time entries back.

In QuoJobIn aworkDirectionDetails
Job with Sync zu awork selectedProjectQuoJob → aworkName: "Number - Title". The customer is taken from the job's customer and created in awork if it doesn't already exist. Start and due dates are taken from the job's start and end dates. The project type is taken from the job type if awork has a type with the same name.
Job numberProject keyQuoJob → aworkOnly for new projects. Task keys then look like HEC-0022-24-7, so you can find a job's tasks by its number.
Job typeProject templateQuoJob → aworkOnly for new projects: the awork template with the same name as the job type, or your default template if there isn't one.
Job pageCustom field QuoJob JobQuoJob → aworkA link on every synced project that opens the job in QuoJob. awork creates the field automatically.
Project Manager and job employeesProject membersQuoJob → aworkThe Project Manager becomes the responsible member. Only people with a matching email address are added.
Headline in a commissioned offerTask listQuoJob → aworkThe same headline in multiple offers for a job is grouped into one task list.
Offer items without a headlineTask listQuoJob → aworkName: "Offer title (offer number)".
Offer itemTaskQuoJob → aworkName and description are taken from the item. The service type becomes the awork activity type. Optional items are skipped.
Hour-based services in a composite serviceSubtasksQuoJob → aworkA composite service is a QuoJob service made up of other services. For example, "SEO Paket M" = 6 h consulting + 8 h frontend + 8 h project management + 6 h layout. Each hour-based service becomes a subtask, with its hours as the planned effort. Materials and other components without hours don't get a subtask.
Planned hours for offer itemsPlanned effort and project budgetQuoJob → aworkOnly for internal hour services (hours): the quantity in hours. For the unit "day," awork calculates quantity × the hours set for the service type. For a composite service, the subtasks contain the hours and the task itself has none. The project budget is the sum of all tasks and subtasks.
Hour bookingTime entryawork → QuoJobCreated, updated, and deleted along with the awork time entry.
Approved vacationAbsenceQuoJob → aworkHalf days are supported for one-day vacation. The comment becomes the description.
Full-day sick leaveAbsenceQuoJob → aworkSick leave for part of a day is skipped.
Attribute awork ProjektProject linkawork → QuoJobOpens the awork project directly from the job.

Only commissioned offers are synced, including offers commissioned internally. Offers that haven't been commissioned and canceled offers stay in QuoJob.

How awork chooses the service type for an hour booking. QuoJob only accepts hours for hour-based services. awork uses the first matching option:

  • The service type linked to the task: the type on a subtask, or the type on the offer item if it accepts hours.
  • A QuoJob hour-based service with the same name as the awork activity type on the time entry.
  • The person's productive default service type in QuoJob. For time entries booked to the fallback user, awork uses the fallback user's productive default service type.

Time entries on awork projects that aren't linked to a QuoJob job stay in awork. A running timer is booked as soon as it stops.


When synchronization happens

Time entries reach QuoJob within seconds. Changes in QuoJob reach awork at the next check, which runs every 5 minutes by default.

DataSynchronization
Jobs, quotes, and employees (QuoJob → awork)At every check, which runs every 5 minutes by default. QuoJob can't notify awork about changes, so awork checks regularly.
Absences (QuoJob → awork)At the same check. awork reads absences from 60 days in the past through 400 days in the future.
Time entries (awork → QuoJob)As soon as someone saves, changes, or deletes a time entry.
Nightly reconciliationOnce each night between 2 and 5 a.m. UTC (4 to 7 a.m. Central European Summer Time). awork books any entries from the past 24 hours that didn't come through, and removes bookings whose awork entry has been deleted.
Manual resyncOn request. awork Support can resend time entries for one entry, a date range, the last few days, or a project.

awork only checks active jobs. When a job in QuoJob moves to finished jobs, for example with the status Abgeschlossen, Abgebrochen, or Inaktiv, synchronization for that job stops and the awork Projekt stays as it is.


Editing synchronized data

Change the plan in QuoJob and the work in awork. Each tool is responsible for specific fields, and synchronization overwrites changes made on the other side.

ObjectControlled by QuoJobCan be changed freely in awork
ProjectName, start date, due date, and time budget. awork resets these at every check.Project key, description, customer, project type, color, status, visibility, and all other settings
Project membersEmployees assigned to the job in QuoJob. If you remove someone in awork, they'll be added back at the next check.Add more members. Synchronization never removes anyone.
Task listWhich lists exist. If you delete a list in awork, it'll come back with its tasks.Name and order
Task and subtaskName, description, and planned effort, but only when the position or the Aufbauleistung changes in QuoJobStatus, assignees, priority, start and due dates, order, list, your own subtasks, comments
Time entryNothingEverything. Correct time entries in awork: the next change in awork overwrites the hours booking in QuoJob. If you move an entry to a project without a QuoJob job, awork deletes its booking.
AbsenceDates, whether it's a half day, and commentNothing: change absences in QuoJob.

A task you delete in awork stays deleted, along with its subtasks, until its position changes in QuoJob. A deleted subtask comes back if its hours change. If you remove a position in QuoJob, its task remains in awork. So delete the task in awork too.


Good to know

  • Subjobs with their own project (default). Each checked subjob gets its own awork Projekt. If its parent job is also synchronized, the awork field QuoJob Hauptprojekt links to that job's project.
  • Merged subjobs. Checked subjobs become task lists in their parent job's project, with the subjob number at the beginning of the name. Their tasks use the parent job's project key, and the QuoJob Job link opens the parent job. Time entries on these tasks are still booked to the subjob in QuoJob. If the parent job is finished, synchronization of its merged subjobs stops too.
  • Stop synchronizing a job. Uncheck Sync zu awork. The awork Projekt remains, and QuoJob will no longer update it.
  • Deleted projects. If you delete a synchronized project in awork, awork won't create it again. awork Support can restore it, and synchronization will then continue. To create a new project, uncheck the box on the job, wait for a check to run, then check it again.
  • Finished jobs. When a job in QuoJob moves to finished jobs, awork leaves the project open. Close or archive it yourself in awork.
  • Canceled quotes. Their tasks remain in awork. Delete them there if the work is no longer needed.
  • Job link. The QuoJob Job link only displays the job if you're logged in to QuoJob. Otherwise, QuoJob displays the login page and then the home page. Click the link again after logging in.
  • Project key. awork uses the job number only when it creates a project. If the number is longer than 32 characters or another project already uses that key, awork creates its own. Changing the job number won't change the key, so existing task keys remain valid.
  • Templates by job type. The template only applies when awork creates a project. Changing the job type won't change existing projects.
  • Changed Aufbauleistung. QuoJob gets the components of an Aufbauleistung from the job's price list. If you change an Aufbauleistung in QuoJob, the subtasks and budget also change for jobs that ordered it previously. If you remove a service type from the Aufbauleistung, its subtask and time entries remain, but it loses its planned effort.
  • Time entries on an Aufbauleistung task. QuoJob doesn't accept hours directly on an Aufbauleistung. So awork books time entries on this task to the person's productive default service type. Track time on the subtasks to have it booked to the correct service type.
  • Employees without a matching email address. They won't be added to projects, and their absences won't be transferred. Their time entries only reach QuoJob through a fallback user.
  • Fallback user. If someone later gets their own QuoJob user, their bookings will be moved to that user the next time something changes or a resync runs. Bookings for people whose user mapping is later removed, for example after they leave the company, stay where they are. awork won't automatically book older failed time entries: ask Support for a resync. If you change a fallback booking in QuoJob, the next change in awork overwrites it.
  • Booking level. Hours are booked in QuoJob against the job and service type, not the individual quote line item.
  • Start and end times. If a time entry starts and ends on the same day, QuoJob receives both times. Otherwise, QuoJob receives the date and the number of hours.
  • Vacation requests. Requested vacation appears in awork only after it's approved. Canceled or rejected vacation disappears from awork.

Troubleshooting

Most issues have one of three causes: a missing checkbox, a quote that hasn't been commissioned yet, or an email address that doesn't match.

ProblemWhat to check
A job doesn't appear in aworkIs Sync zu awork checked? Is the job an active job? Wait for the next check, which runs every 5 minutes by default.
No jobs are being synchronizedHas an attribute been renamed or deleted in QuoJob? Has the technical user's password changed? Give awork Support the new name or password.
A project has no tasksHas the quote been commissioned or commissioned internally? Are the positions marked as optional?
A task has no planned effortOnly internal hour services have planned effort. Other service types create tasks without effort. For an Aufbauleistung, the hours are on the subtasks.
An Aufbauleistung has no subtasksIs the technical user allowed to see sales prices? Only hourly services within the Aufbauleistung become subtasks.
The project key isn't the job numberThe project was created before awork started using job numbers as keys, the number is longer than 32 characters, or another project is already using the key.
The QuoJob Job link opens the home pageLog in to QuoJob and click the link again.
A time entry is missing in QuoJobIs the project linked to a QuoJob job? Does the person's email address match, or is a fallback user set up? Do the task, activity type, or the person's default service type correspond to a QuoJob hourly service? Is the entry dated before the start date for time entries? After a connection error, awork waits until Support has checked QuoJob to make sure nothing is booked twice.
Time entries on an Aufbauleistung are booked to the wrong service typeQuoJob doesn't accept hours on an Aufbauleistung. Track time on the subtasks instead.
An hours booking changed backYou edited it in QuoJob. Correct time entries in awork instead.
Someone is missing from a projectDoes their internal email address in QuoJob match their work email address in awork? Hidden QuoJob employees are skipped.
A deleted task list came backThe list still exists in QuoJob. Change the quote in QuoJob to remove it permanently.
An absence is missingIs absence syncing enabled? Has the vacation been approved? Sick leave for part of a day is skipped.

Still stuck? Contact awork Support with the job number or time entry. Support can view a log for every job and time entry, and can resend time entries to QuoJob.


FAQ

Is the integration free?

Yes, you can use the QuoJob integration free of charge.

What data is synced between QuoJob and awork?

Jobs, commissioned quotes, employees, and optionally absences are transferred from QuoJob to awork. Time entries are synced back to QuoJob from awork.

How often does awork check QuoJob?

By default, every 5 minutes. You can set the interval to anywhere between 1 minute and 24 hours.

Can I enable syncing for individual jobs?

Yes. To do this, select the Sync zu awork checkbox for the relevant job in QuoJob.

Why isn't a quote imported as a task?

Only commissioned and internally commissioned quotes are synced. Uncommissioned, canceled, and optional items are not imported.

Where should I track my time?

Track your time in awork. For a setup service, track your time on the subtasks so the correct service type is used.

Can I correct time entries in QuoJob?

Make corrections in awork. If you later edit a time entry in awork, it may overwrite the time entry in QuoJob.

What happens when a job is completed in QuoJob?

Syncing stops. The existing awork Projekt remains and you'll need to close or archive it there yourself.

Last updated HappySupportPowered by happysupport.ai
© 2026 HappySupport. All rights reserved.