Resources · Make integration

Weekdone Make integrationAutomate Weekdone with Make.

Can your Weekdone items and objectives move on their own? The Weekdone Make integration gives you 10 modules: 2 triggers, 6 actions and 2 searches. This guide is for team leads who plan in Weekdone and walks you from the connection to a working first scenario.

Try the Weekdone integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Weekdone Make integration do for you?

The Weekdone Make integration links your Weekdone account to Make, a no-code tool where you build a scenario, meaning an automation made of connected steps. Each step is a module: it watches Weekdone for new items or objectives, creates or edits them, or lists what already exists.

Objectives that spread to other tools. Watch Objectives notices every new objective in Weekdone, so a scenario can pass it to your project tracker or a shared sheet without anyone copying it by hand.

Items born from other apps. A form answer, a ticket or a CRM deal can become a Weekdone item through Create an Item, so the weekly plan reflects work that started somewhere else.

Tidy plans on demand. List Items and List Objectives pull what is already in Weekdone; pair them with Update an Item or Delete an Objective to correct or remove leftovers in bulk.

Know the limits: the two triggers are scheduled, so Make checks Weekdone on the scenario's schedule instead of hearing about changes the moment they happen, and there is no generic API call module for anything the 10 modules do not cover. Many Make apps also exist as an n8n node, so check whether Weekdone does; the n8n vs Make comparison lays out the two tools side by side. To go further, the Make training teaches scenario building, and the Make agency can build it with you.

Connect

How do you connect Weekdone to Make?

  1. 01

    Register an application in Weekdone

    In Weekdone, open the settings page, go to the Applications tab and add a new application. Give it a name and a URL, paste the callback URI https://www.integromat.com/oauth/cb/weekdone, then click Create.

  2. 02

    Copy your two credentials

    Weekdone now shows a Client ID and a Client secret. Copy both somewhere safe for a moment: Make needs them to prove the connection, which is your Weekdone account linked to Make once and reused by every Weekdone module.

  3. 03

    Create the connection in Make

    Add any Weekdone module to a scenario and click Create a connection. The Connection name field is optional but handy if you manage several accounts. Paste the credentials or follow the on-screen steps.

First scenario

Your first scenario: tag every new Weekdone item

GoalWhen a new item appears in Weekdone, Make picks it up and updates it so it follows your team's naming rule.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for Weekdone and pick Watch Items.

  2. 02

    Link your account

    Click Create a connection and paste the Client ID and Client secret from Weekdone. Once connected, Make can read your Weekdone data and fill in the lists for you.

  3. 03

    Add the update step

    Click the + on the right of Watch Items and choose Update an Item. Map the item from the first module, so each bundle (one item passing between modules) updates the right record.

  4. 04

    Test with Run once

    Create a test item in Weekdone, then click Run once. Open the bubbles above each module to read the bundle it received and check the item was updated as planned.

  5. 05

    Schedule and switch on

    Click the clock on Watch Items to set the schedule; a new scenario runs every 15 minutes by default. Switch the scenario on, and Make keeps checking for new items from then on.

Triggers

What can start a Weekdone scenario?

2 modules start a scenario when something happens in Weekdone. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Weekdone as soon as it happens.

Weekdone1Watch Items

Watch Items

Scheduled trigger

In Make“Triggers when a new item is created.”

Watch Items starts your scenario each time someone adds a new item in Weekdone, and hands that item to the next module as a bundle you can map anywhere.

How it fires
scheduled, so Make checks Weekdone on the scenario's schedule, every 15 minutes by default, and at least 15 minutes apart on the Free plan.
When to use it
when new plan items should appear in a task board, a chat channel or a report without anyone retyping them.
Watch out
it only reacts to new items. An edit to an existing item will not start the scenario.
Weekdone2Watch Objectives

Watch Objectives

Scheduled trigger

In Make“Triggers when a new objective is created.”

Watch Objectives wakes up your scenario when a fresh objective is created in Weekdone, passing its details along so the rest of the flow can act on the goal at the next check.

How it fires
scheduled; Make asks Weekdone on the scenario's schedule rather than being alerted by Weekdone, so there is a short gap between creation and processing.
When to use it
when a newly set objective should be announced to the team or copied into the tool where the work actually gets tracked.
Watch out
updated or deleted objectives are not picked up, only new ones. Pair it with List Objectives if you need the current state.
Modules

What can Make do in Weekdone?

Weekdone gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Weekdone1

Create an Item

Action

In Make“Creates a new item.”

Create an Item adds a new item to Weekdone from data that arrived elsewhere, so your plan fills itself as work comes in from forms, tickets or other apps.

When to use it
when a support ticket or a signed deal in another tool should turn into a line in your team's Weekdone plan.
Watch out
if the same scenario also watches new items, it can pick up the ones it creates; filter them out.
Weekdone2

Create an Objective

Action

In Make“Creates a new objective.”

Create an Objective sets up a new objective in Weekdone without opening the app, which keeps goals in step with decisions logged in other tools.

When to use it
when a goal approved in a spreadsheet, a form or a planning doc should land in Weekdone as a real objective.
Watch out
each run creates a new objective, so running the scenario twice on the same source row gives you a duplicate.
Weekdone3

Delete an Item

Action

In Make“Deletes an item”

Delete an Item removes one item from Weekdone, which helps clear cancelled or duplicated work so the plan shows only what still matters.

When to use it
when a task cancelled in your project tool should also disappear from Weekdone.
Watch out
treat every deletion as final. Test it with Run once on a dummy item before you point it at real data.
Weekdone4

Delete an Objective

Action

In Make“Deletes an objective”

Delete an Objective takes an objective out of Weekdone entirely, handy for cleaning up goals that were created by mistake or dropped along the way.

When to use it
after List Objectives has found duplicates or test objectives you want gone.
Watch out
there is no recycle step in the scenario. Add a filter before this module so only the objectives you really mean to remove reach it.
Weekdone5

Update an Item

Action

In Make“Updates an item.”

Update an Item edits an existing Weekdone item in place, so its details stay accurate without anyone going back into the plan to fix them.

When to use it
when a task changes in another tool and the matching Weekdone item should reflect it, or right after Watch Items to apply a naming rule.
Watch out
you need the right item to target; map it from a trigger or from List Items.
Weekdone6

Update an Objective

Action

In Make“Updates an objective.”

Update an Objective changes an objective that already exists in Weekdone, keeping goals aligned with what happens in the rest of your stack.

When to use it
when a goal is reworded elsewhere and Weekdone should follow instead of drifting out of date.
Watch out
pick the objective from Watch Objectives or List Objectives first; this module edits one objective per bundle.
Weekdone7

List Items

Search

In Make“Lists all items”

List Items returns the items stored in Weekdone, giving your scenario the full picture to report on, compare or clean.

When to use it
when you want to send a digest of current items to a sheet, or feed them one by one into Update an Item.
Watch out
it is a search, so it can return zero, one or many bundles, and every following module runs once per bundle, using operations each time.
Weekdone8

List Objectives

Search

In Make“Lists all objectives”

List Objectives pulls every objective from Weekdone, so you can check, export or sync your goals in one pass instead of opening them one by one.

When to use it
when you want a goal overview in another tool, or need to find an objective before updating or deleting it.
Watch out
many results mean many bundles; each module after it counts one operation per bundle on your plan.
Need help

Need help automating Weekdone with Make?

A person reads every message.

FAQ

Weekdone and Make: common questions

01Is the Weekdone Make integration free?
Yes. Weekdone is a standard app in Make, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your Weekdone subscription is separate and depends on Weekdone's own pricing.
02What do you need to connect Weekdone to Make?
You need an active Weekdone account and a registered application inside it. In the Weekdone settings, the Applications tab lets you add one with a name, a URL and the callback URI given by the Make documentation. Weekdone then displays a Client ID and a Client secret. In Make, add a Weekdone module, click Create a connection, optionally name it, and paste those two values. The connection is then reused by every Weekdone module in your scenarios.
03Do Weekdone triggers fire instantly in Make?
No. Both Watch Items and Watch Objectives are scheduled triggers: Make polls Weekdone on the scenario's schedule rather than receiving a webhook call. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval between two runs, while paid plans can go down to 1 minute. If you need a faster reaction, shorten the schedule on a paid plan rather than expecting an instant signal from Weekdone.
04What if a Weekdone module is missing in Make?
It depends on what you need. The Weekdone app in Make has 10 modules covering items and objectives: watch, create, update, delete and list. It has no Make an API Call module, so anything outside those 10 modules cannot be reached through a generic request. You can often work around it by combining List and Update steps, or by handling that part in another app. For a specific case, the team can look at your setup and suggest a path.
05Should you use Make or n8n for Weekdone?
It depends on the tool your team already uses. Many apps available in Make also have an n8n node, so first check whether one exists for Weekdone. On the Make side, you get 10 ready modules, a visual editor where you test with Run once, and a Free plan with 2 active scenarios. Compare what each tool covers for your exact use case, then choose the one your team will be comfortable maintaining over time.
Same platform

Other docs you might need on this stack.

Browse all integrations