Lead records
Send a lead with at least an email address or phone number. Include a stable event identifier and the appropriate channel when available, so repeated delivery does not create another copy of the same event.
Make + Monthwrap
Your own data reporting
Make workflows that feed your client reports.
Use an HTTP step in Make to send client leads and dated custom numbers into Monthwrap, with fields mapped to the reporting result you need.
AvailableHTTP webhook
Inside the monthly reportSample data
Northside Operations / Fieldwork Studio
From booking event to client record
InputNew bookingAn event in the agency’s own workflow
DestinationOne clientA client-specific Monthwrap webhook
Report measureBooked consultsA named custom number
Booking toolEvent received
Make scenarioFields mapped
HTTP requestResult checked
MonthwrapClient updated
Illustrative HTTP workflow. Monthwrap is not presented as a native Make marketplace module.
Make, at a glance.
- Connect with
- HTTP webhookUse Make’s HTTP module to send the agreed fields to the client’s Monthwrap webhook. This is not a native Make marketplace app.
- Updates
- When your workflow sends a lead or dated number. Your workflow controls its timing.
- Earlier months
- Send earlier dated numbers you retain in the source system. Choose replacement or increment mode deliberately.
- In your report
- Leads and custom numeric results from your scenarios.
Built around your client’s questions
Keep the process that already knows the answer.
For agencies that already coordinate client operations in Make.
An agency may already use Make to route inquiries, update a CRM or collect a daily operations summary. Rebuilding that workflow just to report its result creates another place for the same logic to drift. Instead, send the relevant lead or numeric outcome to the client’s Monthwrap destination.
Use Make’s HTTP module to call the configured webhook, mapping fields from earlier steps in the scenario. The workflow decides when an event is ready and what it means; Monthwrap receives the agreed fields for reporting. Start with one client and one outcome, verify the result and expand only when the definitions are settled.
Choose the numbers that matter
What Make
brings to the report.
Leads and custom numeric results from your scenarios. Choose the relevant figures, add comparisons where the data supports them, and explain what changed.
Daily totals
Send named numeric results for a date, such as consultations booked or calls answered. Use replacement mode when the scenario sends a full daily total or a corrected total.
Event-by-event counts
Use increment mode when each successful workflow event should add to a measure. Design retries carefully because repeating an increment can add the same amount again.
Client-specific context
Each webhook belongs to a client. Map the source account to the correct destination and use labels that explain the outcome rather than exposing internal automation field names in reports.
For your next client report
A booking workflow already in Make
After the booking is accepted by the source system, send its contact details or agreed numeric result to Monthwrap. Keep the definition distinct from a booking request that has not yet been confirmed.
Arrange the report in your own layoutRead it from the client’s side
See the complete
local growth report.
A full fictional agency report, with the work delivered, the numbers behind it and the plan for next month. Use its structure to plan your own mix of sources and client results.
Open the sample reportMake the connection
From Make
to the right client.
Use Make’s HTTP module to send the agreed fields to the client’s Monthwrap webhook. This is not a native Make marketplace app.
Connection methodHTTP webhookAvailabilityAvailableYour connected account’s API permissions and plan apply.
- 01
Create the client destination
In the client’s Sources area, create a webhook and retain the address securely. Use the lead route for contact records or the number route for dated metrics.
- 02
Add a Make HTTP request
Configure a POST request with a JSON body and map the required fields from the earlier modules. This uses Make’s HTTP module, not a native Monthwrap marketplace app.
- 03
Test the result and retry path
Run an agreed test, inspect the response and confirm the record in the correct client. Decide how the scenario handles errors and retries before letting it run unattended.
Know what each
number means.
Field mapping is part of setup
A webhook is a destination, not an automatic connector for every application in Make. The agency defines the source fields, event timing and metric labels.
Keep webhook addresses private
Anyone holding the address can submit data for that client. Store it in the scenario’s protected configuration, keep it out of reports and replace it if it is exposed.
Before you connect
A few useful
answers.
Is there a native Monthwrap app in Make?
This route uses Make’s HTTP module to send a configured JSON request. It is not a native Monthwrap marketplace module, and the scenario needs explicit field mapping and testing.
Should I send a daily total or add one per event?
Use replacement mode for a complete daily total and increment mode for individual counts. Choose deliberately: retrying a replacement keeps the total, while repeating an increment may count the event again.
Can one scenario report several clients?
Yes, if the scenario reliably maps each source account to its own client-specific destination. Test that routing carefully; a technically successful request to the wrong webhook would put data in the wrong client.
Start with your next client report
The data has a source.
The story has your name.
Bring your sources together, choose your layout and add the context your client needs.
Start free trial14-day free trial. No card needed.