Freelo Make integrationAutomate Freelo with Make.

Brings an archived Freelo project back to life so the team can work in it again. Useful when a past client returns and you would rather reuse the old history than start a blank project.

Moves a finished project out of the way while keeping everything inside it. Your active list stays short, and the work can come back later with Activate a Project.

Opens a brand new, empty project in Freelo from data your scenario already has, such as a client name from a form. It saves the copy and paste that usually starts every new job.

Starts a project from a template you already keep in Freelo, so every client gets the same proven setup. It is the quickest route to a project that is ready on day one.

Removes a project from Freelo for good. It keeps the workspace clean when test projects or duplicates pile up after an import or a faulty scenario run.

Fetches the full record of one project so later modules can use its details in a message, a document or a report. You get one project, not a list.

Returns the projects other people have invited your account to, which is handy for freelancers and subcontractors who work inside client workspaces. Each project comes out as its own bundle.

Gives your scenario every project you can see, the ones you own and the ones assigned to you. Think of it as the full inventory before a sync or a cleanup.

Narrows the list to projects your account owns, leaving invitations aside. That keeps a sync focused on the work you are responsible for.

Pulls the to-do lists from Freelo so you can pick the right one before adding tasks. Each list becomes a bundle you can filter by name.

Reads a single to-do list in depth, useful when a trigger tells you a list changed and you want its current state. The result feeds a summary, an alert or a copy elsewhere.

Adds a fresh to-do list inside a project, so a new phase or deliverable gets its own space automatically. Tasks created next can land straight in it.

Marks a Freelo task as done from outside Freelo, so work closed elsewhere shows as closed here too. Your board stays honest without double entry.

Returns tasks across your Freelo account, a wide view for reports, audits or exports. Every task arrives as a separate bundle you can filter.

Focuses on the tasks of one to-do list, which is often all a scenario needs. Fewer bundles means a clearer run and fewer operations.

Turns an outside event into a Freelo task so requests stop living in inboxes. A form answer, an email or a chat message can each become a task with its own title.

Loads the full content of one task, the step you add when a trigger or a search only gives you a reference. After it, every detail of the task is available to map.

Changes an existing task instead of making a new one, so information from other tools flows into the same record. The task keeps its history and comments.

Removes a task entirely, which suits duplicates or tasks created by a test run. The board loses the clutter in a single step.

Reopens a task that was finished, handy when work comes back after delivery. The task returns to the active board with its past intact.

Shows the smaller steps hidden under one task, each returned as a bundle. That lets a scenario check progress at a finer level than the parent task.

Breaks a task into concrete steps automatically, so a standard request always arrives with its checklist. People see what to do without writing it out.

Collects comments from Freelo as separate bundles, ready to archive, search or summarize elsewhere. It is the catch-up tool, where the trigger is the live one.

Posts a comment on a task from your scenario, so outside updates appear where the team already looks. A payment received or a file uploaded can show up in the task thread.

Adds a new label to Freelo, so your tagging system can grow with the data coming from other tools. Labels help people sort tasks at a glance.

Logs time in Freelo from another source, for example a time tracker or a calendar event. Hours end up next to the tasks they belong to.

Retrieves logged time as a set of bundles, the raw material for totals and billing checks. Add an aggregator after it when you need one sum rather than many rows.

Brings the invoices issued in Freelo into Make, where accounting tools and sheets can pick them up. No manual export between systems.

Reads one issued invoice in full, useful when you already know which invoice you are dealing with. Its details can then go into an email or a payment check.

Updates the status of an invoice in Freelo so it matches what happened in your billing system. Both sides then tell the same story.

Returns the people in your Freelo account, which is the easiest way to find who should own a task or receive a message. Each user arrives as a bundle.

Sends project invitations to email addresses, a good fit for clients or freelancers who may not be in Freelo yet. Access happens without an admin doing it by hand.

Adds people to a project without going through a list of email addresses. It suits internal staffing on a new project.

Lists files stored in Freelo so you can back them up, rename them in another tool or share them onward. Each file is its own bundle.

Retrieves a specific file from Freelo so the next module can store, send or attach it. You work with the actual file, not only its name.

Opens the rest of the Freelo API to your scenario, reusing the connection you already made. Anything the other modules skip can still be reached this way.