Resources · Make integration

Earned Value Make integrationAutomate Earned Value with Make.

Stop retyping projects, tasks and hours into Earned Value by hand. The Earned Value Make integration offers 10 action modules and no trigger. This page is for project leads new to Make: connect your account, then build a first scenario that fills Earned Value on its own.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Earned Value Make integration do for you?

The Earned Value Make integration lets Make write into your Earned Value account for you: it creates projects, tasks, time entries and expenses, edits tasks and hours, and deletes what is no longer needed. It has no trigger of its own, so another app or a schedule starts each scenario, meaning the automation you build in Make.

A project that sets itself up. When a deal is marked as won in your sales tool, Create a Project opens the project in Earned Value and Create a Task adds the first work items, so nobody copies the client name twice.

Hours that land where they belong. A timer app or a form can send each finished work session to Create a Time Entry, and Edit a Time Entry fixes the duration when someone corrects it at the source.

Costs recorded at the moment they happen. An approved receipt in your accounting tool becomes a line through Create an Expense, which keeps the project budget honest without a spreadsheet in between.

Know the limits before you start. Make itself says its documentation for Earned Value is incomplete, because little public information exists about the app, so each module is best explored with a test run. There is no search module either, and Make an API Call is the route for anything the listed modules skip. If you are weighing tools, read n8n vs Make; to learn the editor step by step, the Make training covers it.

Connect

How do you connect Earned Value to Make?

  1. 01

    Add an Earned Value module

    Open a scenario, click the +, search for Earned Value and pick any of its modules. In the panel that opens, click Create a connection. A connection is your Earned Value account linked to Make once and reused by every module of the app.

  2. 02

    Name the connection

    This step is optional, yet it helps later. Give the connection a name that says whose account it is, for example the team or the client workspace, so you pick the right one when you add the next Earned Value module.

  3. 03

    Authorize Make, then save

    Depending on what Earned Value asks for, approve access on its page or paste the key the app gives you. Click Save. From now on, the modules of the app can read the projects and tasks your account has access to.

First scenario

Build your first scenario with Earned Value

GoalWhen a deal is won in another app, Make creates the project in Earned Value and adds its first task.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Because Earned Value has no trigger, the first module comes from the app where the event happens, such as your CRM or your form tool.

  2. 02

    Add Create a Project

    Click the + to the right of that first module, search for Earned Value and choose Create a Project. Link your connection, then map the client or deal name coming from the first module.

  3. 03

    Chain Create a Task

    Add Create a Task after the project module. Map the project that was just created, so the task lands in the right place, then write the task name you want every new project to start with.

  4. 04

    Test with Run once

    Click Run once and trigger a test event in the first app. Open each module to read the bundle it received, meaning the item passed along, and check the project in Earned Value.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; on the Free plan, 15 minutes is also the shortest gap. Then switch the scenario on.

Modules

What each Earned Value module does

Earned Value gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Earned Value1

Create a Project

ActionIn the docs only

You get a new project in Earned Value without opening the app, named from data another module sends. It is usually the first Earned Value step of a scenario, since tasks, hours and expenses need a project to belong to.

When to use it
a signed quote or a won deal elsewhere should open the matching project right away.
Watch out
if the same event can fire twice, you get two projects, so test the source with Run once first.
Earned Value2

Create a Task

ActionIn the docs only

This module adds a work item to a project, which saves you from rebuilding the same checklist by hand. Chained after Create a Project, it lets a fresh project arrive with its first tasks already in place.

When to use it
a request comes in through a form or a ticket and should become a task the team can plan.
Watch out
map the project from the previous module instead of typing it, or every task lands in one project.
Earned Value3

Create a Time Entry

ActionIn the docs only

Hours worked show up in Earned Value as soon as another tool records them, so the project figures stay current without anyone copying timesheets. Each bundle that reaches the module becomes one entry, and each one counts as an operation, a single run of a module on your Make plan.

When to use it
a timer app or a daily form already captures who worked on what.
Watch out
a long list of sessions means as many operations.
Earned Value4

Create an Expense

ActionIn the docs only

Costs reach the project record in Earned Value the moment they are approved somewhere else, which keeps the budget view honest. Pick it over Create a Time Entry whenever the line is money spent rather than time worked, such as a purchase or a supplier invoice.

When to use it
a receipt gets validated in your accounting or expense tool.
Watch out
the documentation of the app is limited, so check with Run once which values the module expects.
Earned Value5

Delete Expenses

ActionIn the docs only

Removing expenses from Earned Value keeps the project cost clean when a purchase is cancelled at the source. The plural name suggests it handles more than one expense per run, but the documentation does not confirm how, so check it in a test.

When to use it
a refund or a cancelled order should erase the matching cost line.
Watch out
Make offers no undo button for a deletion, so put a filter before this module.
Earned Value6

Delete Time Entries

ActionIn the docs only

Wrong hours disappear from Earned Value without a manual cleanup, which matters when a timesheet was logged twice or on the wrong project. Choose it over Edit a Time Entry only when the hours should not exist at all.

When to use it
a session is removed in the timer app and Earned Value should follow.
Watch out
treat a deletion as final and run it on test data before activating the scenario.
Earned Value7

Delete a Task

ActionIn the docs only

A task that no longer makes sense leaves the project on its own, so the plan in Earned Value matches what the team really does. It acts on one task per bundle, unlike the two delete modules for hours and expenses whose names point to several.

When to use it
a ticket closed as not planned in your support tool should remove its task.
Watch out
treat the deletion as final and test it on a dummy task first.
Earned Value8

Edit a Task

ActionIn the docs only

An existing task gets updated in place, so a change made elsewhere does not leave Earned Value behind. Prefer it to deleting and recreating the task: the task stays the same one, and the rest of the scenario still points to it.

When to use it
the scope of a request changes in the tool where it was filed.
Watch out
keep a reference to the task from the module that created it, or the scenario cannot tell which task to change.
Earned Value9

Edit a Time Entry

ActionIn the docs only

Corrected hours replace the old ones in Earned Value, which keeps the time already booked without creating a duplicate line. Prefer it to Delete Time Entries whenever the work happened but the duration or the project was wrong.

When to use it
someone fixes a session in the timer app after the fact.
Watch out
the documentation says little about this module, so read the bundle returned by Run once to confirm what changed.
Earned Value10

Make an API Call

ActionIn the docs only

Anything the nine other modules leave out stays within reach: this module calls any endpoint of the Earned Value API with the same connection. It is the answer to the missing search module, for example to look up a project before adding tasks to it.

When to use it
you need to read data or reach an action that has no dedicated module.
Watch out
you write the request yourself, so keep the API reference of Earned Value open while you build it.
Need help

Need help automating Earned Value with Make?

A person reads every message.

FAQ

Questions about Earned Value and Make

01Is the Earned Value Make integration free?
Yes. Earned Value is a standard app, so its modules work on the Make Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 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. Usage is counted in operations, one per module run on one item.
02What does Earned Value need to connect to Make?
An Earned Value account, and that is all the documentation mentions. Make does not list any prerequisite for this app and gives no dedicated connection steps, so the generic flow applies: add an Earned Value module, click Create a connection, optionally name it, then either authorize Make on the Earned Value page or paste the key the app provides, and save. Once saved, the connection is reused by every Earned Value module in your scenarios.
03Does the Earned Value module in Make react in real time?
No, because Earned Value has no trigger in Make at all. All 10 modules are actions, so something else has to start the scenario. You can open it with a trigger from another app, such as a form submission or a won deal in a CRM, and it then reacts as fast as that app allows. Or you can run it on a schedule set on the first module, every 15 minutes by default, with 15 minutes as the minimum on the Free plan.
04What if an Earned Value module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Earned Value API with the connection you already have, which covers what the 10 listed modules leave out, including reading or searching data since there is no search module. Keep in mind that Make describes its own documentation for this app as limited, because little public information about Earned Value exists. Test each call with Run once and read the returned bundle before you rely on it.
05Should Earned Value be automated with Make or n8n?
It depends on the tool you already run and on what the app offers there. On Make, Earned Value comes with 10 modules focused on creating, editing and deleting projects, tasks, hours and expenses, plus a generic API module for the rest, and the editor lets you test each step visually. Apps often have an n8n node too, so check whether one exists for Earned Value and which actions it covers. Compare the two on the exact actions your process needs, not on the name.