How a configurator can connect with Freelo

Projects and deliveryAssessed per project

Freelo is a Czech tool for projects and tasks. Work is split into projects, lists and tasks with due dates and owners, and it publishes an API of its own.

What a configuration could hand over

An accepted order is where the work starts, not where it ends. A project can be created in Freelo with the tasks for the survey, the preparation, the installation and the handover, each carrying a link to the specification. How the tasks are named and who they go to follows your process.

  • Project

    Once an order is accepted, a project named after the customer and the product could be created in Freelo, giving the job one place for the whole team.

  • To-do lists

    The project could hold to-do lists for the survey, the build and the installation, matching the way you split the work today.

  • Tasks

    Each task can get a due date, an assignee and, in its description, the dimensions, options and the link to the 3D preview, so the fitter would not have to dig the specification out of an inbox.

  • Comments

    If the configuration changes after a talk with the customer, the new version could be added as a comment on the task, keeping the history intact.

What we need to connect it

  1. The connection would use the Freelo API v1, authenticating with the email and API key of a user, found in the profile settings.

  2. We recommend a dedicated Freelo user for this, so the history shows clearly what was created automatically.

  3. We need to know when the project should be created: on submission of the configuration, or only after a salesperson confirms the order.

  4. To-do list names, task names and default assignees are written down as the mapping before implementation.

Worth deciding up front

  • Not every enquiry is an order. If a project were created on every submission, Freelo would quickly fill up with projects nobody delivers.
  • Freelo can report events such as a completed task through webhooks. If you want a finished survey reflected back on the enquiry, we design that as a separate step.
  • External fitters with access to the project will see the specification and the customer's contact along with the task, so who belongs in the project needs to be agreed.

Questions about this connection

Can the tasks differ by product type?

Tasks can differ by product type if that is agreed in the mapping. A fence that needs a survey and a garden room that does not could get different task lists.

A salesperson does not have to. If you want the project only after the order is confirmed, the trigger could be a status change on the enquiry in treede CRM instead of manual work in Freelo.

Other integrations

Put Freelo to work in your sales.

Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.

treede is not an official partner or reseller of the systems named here. All names and marks belong to their owners. Integration options are verified during implementation against the system interface and version. Freelo official site