Skip to content
Hypamoon

For teams that run on awork

awork apply project template to old projects

A project created from an awork template starts with its statuses, automations and custom fields. A project that started without the template, or with a different one, keeps its own set, and bringing it in line is done project by project.

How it goes today

  1. Open each older project one by one.
  2. Add the statuses from the template by hand.
  3. Rebuild the automations of the template in each project.
  4. Link the custom fields and copy over the tasks that fit.

How it can go

Existing projects get what your template gives a new one.

You pick a template and the projects it should apply to. For each project you see what it does not have yet: statuses, automations, custom fields and the tasks of the template. After your yes, those are added to the project, the tasks only when you tick them. A list keeps which projects got which template, so after you change the template you run it again for the projects you choose.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your awork key in the portal, never in the chat.

Your request

With Hypamoon, take one of our awork project templates and the projects I choose. Show me per project which statuses, automations, custom fields and tasks from the template it does not have yet. After my yes, add them to the project, with the tasks of the template only when I tick that. Keep a list of which projects got which template, so I can run it again after I change the template.

An admin creates the awork key under Settings, Integrations: add an API client, then Manage API Keys. It stays yours.