Resources · Make integration

Daylite Make integrationAutomate Daylite with Make.

Can Make keep your Daylite CRM moving while you focus on clients? The Daylite Make integration gives you 57 modules: 16 instant triggers, 33 actions and 8 searches. This guide shows you how to link your account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Daylite Make integration automate?

The Daylite Make integration links your Daylite account to Make, a visual tool where you chain apps together without writing code. Daylite tells Make the moment a contact, project, task or opportunity changes, and Make then creates, updates, reads or removes records for you.

Every new lead gets a next step. Watch New Contact fires as soon as someone is added, and Create a Task puts a follow-up on the right person's list, so no lead sits untouched.

Won deals turn into projects. Watch Opportunity Updated catches the change on a deal, and Create a Project opens the delivery file with the client already attached. Sales and delivery stop retyping the same details.

Your other tools stay in sync with the CRM. Watch Company Updated can push a corrected address to a spreadsheet, and Search Contacts checks whether a person already exists before a form adds a duplicate. The Airtable Make integration is a common partner for this kind of sync.

All 16 triggers are instant, so nothing waits for a polling cycle. When a listed module does not cover what you need, Make an API Call reaches the rest of the Daylite API with the same connection. The same app also exists on n8n; the n8n vs Make comparison lays out the differences between the two tools, and the Make training helps you go past the first scenario.

Connect

How do you connect your Daylite account to Make?

  1. 01

    Add a Daylite module

    Log in to Make, open a scenario and add any Daylite module. A connection is your Daylite account linked to Make once, then reused by every Daylite module. Click Create a connection to start it.

  2. 02

    Name the connection

    The Connection name field is optional, yet a clear label such as "Daylite sales team" saves confusion later, especially when several people or several Daylite accounts share the same Make organization.

  3. 03

    Authorize Daylite

    Daylite signs you in with OAuth2, so follow the on-screen instructions or paste the credentials you copied from Daylite. You need an active Daylite account for this step. Once it succeeds, the module shows your connection name.

First scenario

Your first scenario: a follow-up task for every new Daylite contact

GoalWhen a new person is created in Daylite, Make adds a follow-up task so the lead never goes cold.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario, the automation you are about to build. Click the big + to place the first module, the brick that will start everything.

  2. 02

    Add Watch New Contact

    Search for Daylite and pick Watch New Contact. Click Create a webhook, then Create a connection to link your account. The lightning badge means Daylite calls Make as soon as a person is added.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and choose Daylite Create a Task. Map the contact's name from the first module into the task title, so each task says who to call.

  4. 04

    Test with Run once

    Click Run once, then add a test person in Daylite. Each module shows the bundles it received: one bundle is one item passing between modules, here one contact, then one new task.

  5. 05

    Switch it on

    When the test task looks right, switch the scenario on. Each run of a module counts as one operation on your Make plan, so this scenario uses two operations per new contact.

Triggers

Daylite triggers: what can start a scenario

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

Daylite1Watch Form Updated

Watch Form Updated

Instant trigger

In MakeTriggers when a form is updated in DayLite.

You learn the moment someone edits a filled-in form in Daylite, so the corrected answers reach the rest of your stack without a manual export.

How it fires
instant, Daylite calls Make through a webhook as soon as the form changes.
When to use it
an intake questionnaire gets completed after a client call, and you want the final version copied to the project file or a shared sheet.
Watch out
an edit and a creation are separate events, so pair it with Watch New Form if brand new forms matter too.
Daylite2Watch New Appointment

Watch New Appointment

Instant trigger

In MakeTriggers when a new appointment is created in Daylite.

Every appointment booked in Daylite can kick off its own preparation work, from a reminder message to a briefing task for whoever takes the meeting.

How it fires
instant, Daylite notifies Make by webhook the moment the appointment is created.
When to use it
a discovery call lands on the calendar and you want a prep checklist created for the account owner right away.
Watch out
rescheduling an existing appointment is not a new appointment, so this trigger stays silent on moved meetings.
Daylite3Watch New Form

Watch New Form

Instant trigger

In MakeTriggers when a new form is created in Daylite.

A brand new form record in Daylite becomes the starting signal for your scenario, which lets you route fresh answers before anyone opens the CRM.

How it fires
instant, the webhook tells Make as soon as the form exists.
When to use it
a site survey or onboarding form gets added to a client, and the answers should create a task or land in a reporting table.
Watch out
later edits to that same form will not fire it again; that job belongs to Watch Form Updated.
Daylite4Watch New Note

Watch New Note

Instant trigger

In MakeTriggers when a new note is created in Daylite.

Notes your team writes in Daylite stop living in one place: each fresh note can be shared, summarized or attached elsewhere automatically.

How it fires
instant, Daylite pings Make over a webhook when the note is saved for the first time.
When to use it
call notes should appear in the team chat channel of the matching client so colleagues see what was promised.
Watch out
notes can hold sensitive details, so check who can read the destination before you forward the text.
Daylite5Watch New Project

Watch New Project

Instant trigger

In MakeTriggers when a new project is created in Daylite.

Opening a project in Daylite can set up everything around it at once: folders, kickoff tasks, a message to the delivery lead.

How it fires
instant, Make hears about the project through a webhook as soon as it is created.
When to use it
your team opens a project when a job is confirmed, and you want the standard kickoff tasks generated with Create a Task.
Watch out
if a scenario of yours also runs Create a Project, this trigger will see those projects too; plan for it so the flows do not feed each other.
Daylite6Watch New Task

Watch New Task

Instant trigger

In MakeTriggers when a new task is created in Daylite.

Each task added in Daylite can be mirrored where people actually work, such as a team channel or a personal to-do app.

How it fires
instant, Daylite sends the new task to Make by webhook right after it is created.
When to use it
a manager assigns work in Daylite, and the assignee should get a direct message with the task name and due details.
Watch out
tasks created by your own Make scenarios fire it as well, so avoid a loop where a new task leads to another new task.
Daylite7Watch Note Updated

Watch Note Updated

Instant trigger

In MakeTriggers when a note is updated in Daylite.

This trigger catches edits to existing notes, which keeps any copy of that note outside Daylite accurate after someone corrects it.

How it fires
instant, a webhook alerts Make whenever a note changes.
When to use it
meeting notes get cleaned up after the call, and the tidy version should replace the draft you already sent to a shared document.
Watch out
small typo fixes count as updates too, so add a filter in Make if only meaningful changes should go through.
Daylite8Watch Project Updated

Watch Project Updated

Instant trigger

In MakeTriggers when a project is updated in Daylite.

Changes on a Daylite project, like a new stage or a new owner, can ripple out to the tools your clients or your delivery team follow.

How it fires
instant, Daylite calls Make through a webhook each time the project is modified.
When to use it
a project moves to its closing stage and the client should receive a wrap-up message or an invoice reminder task.
Watch out
every edit fires, whatever field changed, so filter on the value you care about before acting.
Daylite9Watch Task Updated

Watch Task Updated

Instant trigger

In MakeTriggers when a task is updated in Daylite.

Progress on Daylite tasks becomes visible outside the CRM, because each modification to a task can update a board, a report or a teammate.

How it fires
instant, the webhook sends Make the modified task as soon as it is saved.
When to use it
a task gets marked done, and the next step in the process should be created for a colleague automatically.
Watch out
updating a task from Make with Update a Task also fires this trigger, a classic loop to guard with a filter.
Daylite10Watch Company Updated

Watch Company Updated

Instant trigger

In MakeTriggers when a company is updated in Daylite.

When company details change in Daylite, your billing tool, spreadsheet or mailing list can receive the same correction without anyone retyping it.

How it fires
instant, Daylite alerts Make by webhook as soon as the company record is edited.
When to use it
an account manager fixes a billing address, and the finance sheet must reflect it before the next invoice goes out.
Watch out
the other system needs a stable key to find the matching row, so store the Daylite company reference there when you first sync.
Daylite11Watch Contact Deleted

Watch Contact Deleted

Instant trigger

In MakeTriggers when a person is sent to the Trash in Daylite.

You find out when a person is sent to the Trash in Daylite, which lets you clean the same contact out of mailing lists and other copies.

How it fires
instant, Daylite informs Make through a webhook the moment the person goes to the Trash.
When to use it
a contact asks to be forgotten, and the removal in Daylite should also unsubscribe them from your newsletter tool.
Watch out
the trigger is about the Trash, so think twice before a scenario permanently deletes data elsewhere for a contact that may be restored.
Daylite12Watch Contact Updated

Watch Contact Updated

Instant trigger

In MakeTriggers when a person is updated in Daylite.

Edits to a person in Daylite, a new phone number or a changed job title, can flow straight into every tool that keeps its own copy of that contact.

How it fires
instant, a webhook pushes the updated person to Make when the change is saved.
When to use it
your email marketing list should always carry the latest address and role your sales team recorded.
Watch out
if another scenario writes back into Daylite with Update a Contact, add a filter so the two flows do not trigger each other.
Daylite13Watch New Company

Watch New Company

Instant trigger

In MakeTriggers when a new company is created in Daylite.

A company created in Daylite can instantly get its counterpart in accounting, a shared folder, or a welcome sequence for the new account.

How it fires
instant, Daylite tells Make by webhook as soon as the company exists.
When to use it
a new client organization is added after a signed quote, and the billing tool needs a customer record before the first invoice.
Watch out
companies added in bulk arrive as many separate runs, each consuming operations on your plan.
Daylite14Watch New Contact

Watch New Contact

Instant trigger

In MakeTriggers when a new person is created in Daylite.

Every new person in Daylite can receive a next step right away, which is the easiest way to make sure no lead waits for someone to remember them.

How it fires
instant, Daylite calls Make through a webhook as soon as the person is created.
When to use it
a trade-show contact or a website lead is entered, and a follow-up task should appear for the account owner.
Watch out
people created by a Make scenario with Create a Contact will fire it too, which matters if the two scenarios are chained.
Daylite15Watch New Opportunity

Watch New Opportunity

Instant trigger

In MakeTriggers when a new opportunity is created in Daylite.

Fresh deals in Daylite can alert the right people and prepare the paperwork, so sales momentum starts the minute an opportunity is logged.

How it fires
instant, the webhook hands the opportunity to Make as soon as it is created.
When to use it
a rep opens a deal, and the sales manager should get a message with the client name and the deal details.
Watch out
a deal opened by mistake still fires the trigger, so any message it sends should be easy to ignore or undo.
Daylite16Watch Opportunity Updated

Watch Opportunity Updated

Instant trigger

In MakeTriggers when an opportunity is updated in Daylite.

Stage changes and edits on a Daylite deal become events you can act on, which is how a won opportunity can hand over to delivery on its own.

How it fires
instant, Daylite notifies Make by webhook each time the opportunity changes.
When to use it
a deal is marked won, and Create a Project should open the delivery project for the same client.
Watch out
the trigger fires on any edit, so add a filter on the stage or status before creating anything, or you will get a project per edit.
Modules

Daylite modules: what Make can do in your CRM

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

Daylite1

Create a Company

Action

In MakeCreates a new company.

Adds a new organization to Daylite from data another app captured, so accounts appear in the CRM without anyone keying them in.

When to use it
a signed quote or a paid invoice in another tool should create the client company in Daylite.
Watch out
run Search Companies first if the company might already exist, or you will end up with duplicates.
Daylite2

Create a Contact

Action

In MakeCreates a new contact.

Turns a form entry, a sign-up or an email sender into a person record in Daylite, ready for your sales team to work.

When to use it
a lead fills in a website form and should land in the CRM with name and email already filled.
Watch out
check with Search Contacts before creating, since the same person often signs up twice.
Daylite3

Create a Form

Action

In MakeCreates a new form.

Fills in a new form record in Daylite from outside data, so questionnaire answers collected elsewhere end up stored with the client.

When to use it
an onboarding survey answered in another tool should be saved in Daylite as a form on the matching account.
Watch out
a form follows a form definition, so use List Form Definitions first to know which template to target.
Daylite4

Create a Form Definition

Action

In MakeCreates a new form definition.

Builds a new form template in Daylite, the blueprint that individual forms are filled from, straight from a scenario.

When to use it
you set up a new service line and want its standard questionnaire template created as part of the setup scenario.
Watch out
this creates the template, not an answered form; that second job belongs to Create a Form.
Daylite5

Create an Appointment

Action

In MakeCreates a new appointment.

Puts a meeting on the Daylite calendar from an event in another app, so bookings made elsewhere show up where your team plans its day.

When to use it
a client books a slot through an online scheduler and the meeting must appear in Daylite too.
Watch out
if both calendars sync back and forth, filter carefully so one booking does not become two appointments.
Daylite6

Create an Opportunity

Action

In MakeCreates a new opportunity.

Opens a deal in Daylite from a qualified signal, which gives sales a pipeline entry without waiting for manual data entry.

When to use it
a prospect requests a quote on your site and a new opportunity should be tracked for the rep who owns the territory.
Watch out
link the deal to an existing contact or company, found first with a search module, to keep the pipeline clean.
Daylite7

Create a Note

Action

In MakeCreates a new note.

Writes a note into Daylite from anything text-based, so emails, call summaries or chat messages sit in the client history.

When to use it
an important client email arrives and its content should be logged as a note on the matching contact.
Watch out
map only the part of the message you need, since pasting full email threads makes notes hard to read.
Daylite8

Create a Project

Action

In MakeCreates a new project.

Opens a delivery project in Daylite automatically, which removes the handover gap between the moment a sale closes and the moment work begins.

When to use it
Watch Opportunity Updated catches a won deal and this module creates the project for the same client.
Watch out
filter on the deal stage upstream, otherwise each edit on the opportunity creates another project.
Daylite9

Create a Task

Action

In MakeCreates a new task.

Drops a to-do into Daylite for the right person, which is the simplest way to turn events from any app into clear next actions.

When to use it
a new contact arrives and the account owner should get a task to call them back.
Watch out
tasks created here also fire Watch New Task, so watch for loops if another scenario listens to it.
Daylite10

Delete a Company

Action

In MakeRemoves a company.

Removes a company record from Daylite through a scenario, handy for cleanup jobs that would take ages by hand.

When to use it
a list of test or duplicate organizations has been identified and must be cleared out of the CRM.
Watch out
a deletion from Make cannot be undone from Make, so run the scenario with Run once on a single record before letting it loose.
Daylite11

Delete a Contact

Action

In MakeRemoves a contact.

Erases a person from Daylite when another system says they should go, keeping your CRM aligned with privacy requests or unsubscribes.

When to use it
a contact asks for their data to be removed and the request is logged in a support tool.
Watch out
confirm the right person with Search Contacts first; deleting a namesake is not something Make can reverse.
Daylite12

Delete a Form

Action

In MakeRemoves a form.

Removes an answered form from Daylite, useful when forms were created by mistake or by an earlier test scenario.

When to use it
you tested Create a Form and now need to clear the dummy records it produced.
Watch out
the module works on one form per run, so pass it the exact records to delete rather than a broad search result.
Daylite13

Delete an Appointment

Action

In MakeRemoves an appointment.

Takes a meeting off the Daylite calendar when it is cancelled elsewhere, so nobody prepares for a call that will not happen.

When to use it
a client cancels through your booking tool and the matching Daylite appointment should disappear.
Watch out
you need a reliable link between the two calendars, stored when the appointment was first created.
Daylite14

Delete an Opportunity

Action

In MakeRemoves an opportunity.

Clears a deal from Daylite, which keeps pipeline reports honest when test entries or duplicates slip in.

When to use it
a duplicate opportunity is spotted by a search step and should be removed while the original stays.
Watch out
a lost deal is often worth keeping for reporting, so consider Update an Opportunity before deleting.
Daylite15

Delete a Note

Action

In MakeRemoves a note.

Removes a note from Daylite, useful when notes were copied in automatically and the copy is no longer wanted.

When to use it
a scenario logged chat messages as notes and you need to clear the ones it added by error.
Watch out
there is no undo from Make, so keep a copy elsewhere if the text might matter later.
Daylite16

Delete a Project

Action

In MakeRemoves a project.

Removes a project from Daylite in one step, which helps when an automated flow opened projects that should never have existed.

When to use it
a deal was marked won by mistake and the project Create a Project opened for it must go.
Watch out
Make cannot bring the project back, so test on a single record with Run once before any bulk cleanup.
Daylite17

Delete a Task

Action

In MakeRemoves a task.

Removes a to-do from Daylite when the work no longer applies, so task lists reflect what people really need to do.

When to use it
an appointment is cancelled and the prep task created for it should vanish too.
Watch out
marking a task done with Update a Task keeps the history, which is usually better than deleting it.
Daylite18

Get a Company

Action

In MakeShows the details of a company.

Reads the full record of one company in Daylite, so later modules can use details the trigger did not include.

When to use it
a new opportunity comes in and you need the company's full details to prepare a quote in another tool.
Watch out
it targets one known company; when you only have a name, start with Search Companies instead.
Daylite19

Get a Contact

Action

In MakeShows the details of an contact.

Fetches everything Daylite holds on one person, giving your scenario the phone, email and role it needs downstream.

When to use it
a task is created for a contact and the reminder message should include how to reach them.
Watch out
it expects one specific person; to find someone by name or email, use Search Contacts.
Daylite20

Get a Form

Action

In MakeShows the details of a form.

Pulls the answers of one filled-in form out of Daylite so they can be copied, analyzed or sent to a client.

When to use it
a form update fires a scenario and you want the complete set of answers to build a summary document.
Watch out
point it at the form handed over by the trigger or an earlier module, not at a form definition.
Daylite21

Get an Appointment

Action

In MakeShows the details of an appointment.

Returns the details of one Daylite appointment, handy when a later module needs the time, place or attendees.

When to use it
a task linked to a meeting fires, and the reminder you send should mention when and where the meeting happens.
Watch out
for several meetings at once, Search Appointments fits better than repeating this module.
Daylite22

Get an Opportunity

Action

In MakeShows the details of an opportunity.

Reads one deal in full from Daylite, which gives a scenario the value, stage and client it needs to act on.

When to use it
a note is added to a deal and the alert to your manager should include the deal's current stage.
Watch out
it reads a single opportunity; building a pipeline report calls for Search Opportunities.
Daylite23

Get a Note

Action

In MakeShows the details of a note.

Retrieves the text and context of one Daylite note so it can be forwarded, translated or stored elsewhere.

When to use it
a note update fires and you want the complete, current text before replacing an old copy in a shared document.
Watch out
map the note from an earlier module; guessing a reference by hand rarely works.
Daylite24

Get a Project

Action

In MakeShows the details of a project.

Pulls one project's full record from Daylite, giving later steps the client, status and dates tied to it.

When to use it
a task on a project is marked done and the status update you post should name the project and its client.
Watch out
it covers one project per run; for an overview of many, use Search Projects.
Daylite25

Get a Task

Action

In MakeShows the details of a task.

Reads a single Daylite task in detail, so a scenario knows who owns it, what it is about and when it is due.

When to use it
a task changes and the notification to the assignee should carry the full description, not just a title.
Watch out
the task to read comes from an earlier module; map it rather than typing a fixed value.
Daylite26

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reaches any part of the Daylite API that the listed modules leave out, using the connection you already set up.

When to use it
you need a Daylite record type or an operation that has no dedicated module in Make.
Watch out
you describe the request yourself, so keep the Daylite API reference open and test with Run once before going live.
Daylite27

Update a Company

Action

In MakeModifies a company.

Writes new values onto an existing company in Daylite, so corrections made in billing or support tools reach the CRM.

When to use it
finance updates a client's legal name in accounting and Daylite should show the same.
Watch out
this change fires Watch Company Updated, so filter any scenario that listens to it to avoid a loop.
Daylite28

Update a Contact

Action

In MakeModifies a contact.

Refreshes a person's details in Daylite from another source, keeping emails, phones and roles current without manual edits.

When to use it
a contact updates their profile in your newsletter tool and the change should land in the CRM.
Watch out
map only the values that really changed, so an old copy from another tool never replaces a fresher detail your sales team typed.
Daylite29

Update a Form

Action

In MakeModifies a form.

Changes the answers of an existing Daylite form, useful when a client corrects information they gave earlier.

When to use it
a client resubmits a questionnaire in another tool and the stored Daylite form should match the new answers.
Watch out
the edit fires Watch Form Updated, so a scenario on that trigger may run again.
Daylite30

Update an Opportunity

Action

In MakeModifies an opportunity.

Moves a deal forward in Daylite from outside events, so the pipeline reflects signed quotes or payments as they happen.

When to use it
an e-signature tool reports a signed contract and the opportunity should switch to its won stage.
Watch out
this fires Watch Opportunity Updated, which may open a project if another scenario listens to it; that is often exactly the goal.
Daylite31

Update a Note

Action

In MakeModifies a note.

Edits the content of an existing Daylite note, letting you append or replace text from another app.

When to use it
a transcription tool delivers a cleaned-up version of a call and the draft note should be replaced with it.
Watch out
map the new content from the transcription step, and keep the draft somewhere if you may want to compare the two versions.
Daylite32

Update a Project

Action

In MakeModifies a project.

Changes a Daylite project's details from outside events, so delivery status follows what happens in your other tools.

When to use it
the final invoice is paid in accounting and the project should move to its closed stage.
Watch out
the change fires Watch Project Updated, so check that no scenario sends the client a message you did not intend.
Daylite33

Update a Task

Action

In MakeModifies a task.

Edits an existing Daylite task, marking it done, reassigning it or changing its details, based on what happens elsewhere.

When to use it
a document gets signed and the "collect signature" task should close on its own.
Watch out
the update fires Watch Task Updated, and a scenario on that trigger that updates tasks again will loop.
Daylite34

List Form Definitions

Search

In MakeGets the list of all form definitions.

Returns every form template defined in Daylite, so your scenario can pick the right one before filling a form.

When to use it
you build Create a Form and need to know which templates exist and how they are named.
Watch out
it sends back several bundles, one per template, so each later module runs once for every template unless you filter.
Daylite35

Search Appointments

Search

In MakeSearches for appointments or lists them all.

Finds Daylite appointments matching your criteria, or lists them all, which is the base for any meeting digest or report.

When to use it
you want a summary of upcoming meetings sent to a team channel.
Watch out
a search can return zero, one or many bundles; plan what the scenario should do when nothing matches.
Daylite36

Search Companies

Search

In MakeSearches for companies or lists them all.

Looks up organizations in Daylite, which lets a scenario check whether a company already exists before creating it.

When to use it
a new customer in your billing tool should be matched with its Daylite company rather than duplicated.
Watch out
with no criteria it lists every company, and every result counts as a bundle flowing to the next modules.
Daylite37

Search Contacts

Search

In MakeSearches for contacts or lists them all.

Finds people in Daylite by what you know about them, the safest first step before creating or updating a contact.

When to use it
a form lead arrives and you want to update the existing person if they are already in the CRM.
Watch out
namesakes can return more than one result, so match on a precise value such as an email when you can.
Daylite38

Search Notes

Search

In MakeSearches for notes or lists them all.

Pulls a set of Daylite notes, or all of them, so you can export client history or scan it for a topic.

When to use it
you prepare an account review and want every note on a client gathered in one document.
Watch out
each note found becomes its own bundle, so later modules run once per note and use operations accordingly.
Daylite39

Search Opportunities

Search

In MakeSearches for opportunities or lists them all.

Gathers deals from Daylite that match your filters, the raw material for a pipeline summary or a stale-deal alert.

When to use it
the sales team wants open opportunities posted to its channel with their stage and owner.
Watch out
a search can come back with zero bundles, so decide in advance what the scenario should do when no deal matches.
Daylite40

Search Projects

Search

In MakeSearches for projects or lists them all.

Lists Daylite projects that meet your criteria, giving you a base for status reports or a sync to a planning tool.

When to use it
you want every active project copied into a shared spreadsheet for people who do not use Daylite.
Watch out
the full list can be long; narrow the search so the scenario does not spend operations on projects you do not need.
Daylite41

Search Tasks

Search

In MakeSearches for tasks or lists them all.

Pulls the tasks sitting in Daylite into your scenario, either the ones matching your search or the whole list, so the next modules can close, reassign or report on them.

When to use it
pick it over Get a Task when you do not have the task ID yet and need to find open work first, such as before sending a team digest.
Watch out
it can return zero, one or many bundles, and every following module runs once per task, which adds operations on your plan.
Need help

Need help automating Daylite with Make?

A person reads every message.

FAQ

Daylite and Make: frequent questions

01Is the Daylite Make integration free?
Yes, Daylite is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between 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 count usage in credits per month. Every Daylite module run is one operation, and the connection still requires an active Daylite account.
02What do you need to connect Daylite to Make?
An active Daylite account is the only prerequisite. In Make, add any Daylite module and click Create a connection, give the connection a name if you like, then sign in to Daylite through OAuth2 or paste the credentials copied from Daylite. For instant triggers, click Create a webhook first, then Create a connection. The documentation also describes advanced options: registering your own OAuth application to get a client ID and client secret, or generating a personal token in Daylite.
03Do the Daylite triggers in Make react in real time?
Yes. All 16 Daylite triggers are instant: Daylite calls Make through a webhook as soon as a contact, company, project, task, note, form, appointment or opportunity is created or changed, or when a contact goes to the Trash. You do not wait for a polling interval, which is why these triggers carry the lightning badge in the editor. The one thing to remember is creating the webhook when you add the trigger, before the connection, otherwise Make receives nothing.
04What if a Daylite module is missing in Make?
Use Make an API Call. It sends any request to the Daylite API with the connection you already have, so a record type or an operation without a dedicated module is still within reach. You write the request yourself, which means reading the Daylite API reference and testing with Run once. The built-in modules already cover companies, contacts, forms, form definitions, appointments, opportunities, notes, projects and tasks. Make also notes that its Daylite documentation is AI-generated from the official one, so check important details with Daylite.
05Should you use Make or n8n for Daylite?
It depends on the tool your team already knows. Daylite has a native app in Make with 57 modules, including 16 instant triggers, and the same app often has a node in n8n as well. Look at which records you need to handle, whether the listed modules cover them, and which editor your team is comfortable maintaining. Make's own offer is described on this page: a Free plan with 2 active scenarios, then paid plans counted in credits. The n8n vs Make comparison on this site goes through the rest.