HacknPlan Make integrationAutomate HacknPlan with Make.

This action puts an existing HacknPlan user on a project, so the person sees its boards and work items without anyone sending an invite by hand. It saves the setup chores that follow every new project.

Marks a milestone as finished, so your planning in HacknPlan reflects what really shipped without someone clicking through the project. Useful at the end of a release flow driven from another tool.

Adds a new board to a project, the place where your team lays out the next batch of work. Creating it from Make means the board exists the moment the plan is agreed elsewhere.

Creates a milestone in a project, turning a date someone agreed on in a meeting or a contract into a target the whole team can see in HacknPlan. No retyping from notes.

Starts a fresh HacknPlan project from a scenario, so a signed deal or an approved pitch becomes a real workspace straight away. Everything else, boards, milestones and members, can follow in later modules.

Turns an outside request into a work item inside HacknPlan: a bug from a form, a task from a chat message, an asset request from a spreadsheet. The team works from one list instead of five inboxes.

Removes a board from a project. It keeps HacknPlan free of empty or test boards that pile up when sprints get planned and then dropped, so the team only sees what is live.

Erases a milestone for good, which is different from closing it. Pick this one when the milestone should never have existed, for example a date created by mistake or for a deal that fell through.

Removes a whole HacknPlan project, the heaviest action in the list. It fits cleanup flows, such as clearing sandbox projects you created only to test a scenario.

Removes a single work item, for when a task or bug is a true duplicate or was logged by mistake. It keeps the backlog clean without a producer hunting for stray entries.

Fetches one board you already know, so later modules can use its details in a message, a report or a decision. It reads only and changes nothing in HacknPlan.

Reads a single milestone so the rest of the scenario can quote it: its name in a chat post, its details in a client update. Safe to run, since nothing is modified.

Pulls the details of one project into your scenario. A read-only step, it is also the safest way to check that a fresh connection really works before you try anything that writes.

Looks up one member of a project, giving later modules the person's details to mention them, route a task or check their role before acting.

Retrieves one work item in full, useful when a trigger or another app only gave you a reference and you need the rest before acting. Nothing changes in HacknPlan.

Your way around missing modules. It calls any endpoint of the HacknPlan API with the connection you already set up, so you are not stuck when the 32 ready modules stop short of what you need.

Takes a person off a project, which closes their access there without touching their other projects. It suits offboarding and the end of a freelance contract.

Brings a closed milestone back to life, so work can continue under the same target without creating a duplicate. It is the counterpart of Close a Milestone.

Changes a board that already exists. The update is partial: only what you fill in is changed, the rest stays as it was. Good for keeping a board in line with decisions taken elsewhere.

Edits a milestone in place, so a shifted target in another tool shows up in HacknPlan without anyone retyping it. Only what you fill in changes.

Adjusts an existing project from a scenario. The change is partial, so you can touch a single detail and keep the rest intact, which is safer than rebuilding a project by hand.

Changes how a member is set up in a project, without removing and re-adding them. The update is partial, so only what you fill in moves.

Edits a work item already in HacknPlan, so status changes made in another tool land in the backlog too. Only what you fill in changes.

Returns every board in a project, each as its own bundle, so you can loop through them for a report or to find the one you need. A search like this can return zero, one or many results.

Gathers the milestones of a project into your scenario, one bundle each. It is the quickest way to build a roadmap view in another tool or to check whether a target already exists.

Gives you all the projects your connected account is a member of, one bundle per project. It is the starting point for anything that spans the whole studio, like a portfolio report.

Returns the people on a project, one bundle per member, so you can audit access or message the whole team from another tool.

Finds work items that match what you ask for, or lists all of them if you leave the search open. Each result comes out as a separate bundle for the next module.