Validated lead events
Send an event with contact information and a stable identifier after the workflow’s own checks. Monthwrap accepts an email address or phone number; it does not inherit every validation rule from your source system.
n8n + Monthwrap
Your own data reporting
n8n workflows that feed your client reports.
Use n8n’s HTTP Request node to send client leads or dated custom numbers to Monthwrap from a workflow your agency controls.
AvailableHTTP webhook
Inside the monthly reportSample data
Harbor Operations / Oakline Services
An operations result, ready to report
Source resultJobs completedA definition agreed with the client
DeliveryDaily totalReplacement mode for the chosen date
DestinationClient reportA named custom metric in Monthwrap
Operations systemRead the result
n8n workflowPrepare the day
HTTP RequestSend and check
MonthwrapRecord the total
Illustrative configured workflow. n8n cloud or self-hosted execution must be able to reach the Monthwrap API.
n8n, at a glance.
- Connect with
- HTTP webhookUse an HTTP Request node and map the expected fields to the client’s webhook. No native Monthwrap node is required.
- 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 workflows.
Built around your client’s questions
Your workflow can keep the business logic.
For agencies using n8n to connect operational tools and custom data.
A workflow may already know which jobs are complete, which consultations were attended or which leads passed an internal check. Those definitions often live outside an advertising platform. Sending the agreed result into Monthwrap lets the report reflect the client’s operation without copying the entire workflow into the reporting tool.
Use an n8n HTTP Request node to send a mapped payload to the correct client destination. Keep validation and routing in the workflow, choose whether a number replaces a daily total or adds an event, then verify the response. The report can show the result beside platform data with a label the client understands.
Choose the numbers that matter
What n8n
brings to the report.
Leads and custom numeric results from your workflows. Choose the relevant figures, add comparisons where the data supports them, and explain what changed.
Operational daily totals
Prepare a named numeric result for a specific date. Replacement mode suits totals that may be recalculated later, such as completed jobs for the previous day.
Incremental counts
Use increment mode for an agreed event count when the workflow can manage repeat execution. Do not assume that retrying an incremental request is the same as replacing a daily total.
Source and channel context
Keep useful channel and event-time fields with leads. For numeric measures, agree the label and unit so a custom field does not become an unexplained number in the monthly report.
For your next client report
A workflow with custom validation
Let n8n check the source record before sending a lead to the client workspace. Explain the qualification rule separately; a received lead is not automatically a won opportunity.
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 n8n
to the right client.
Use an HTTP Request node and map the expected fields to the client’s webhook. No native Monthwrap node is required.
Connection methodHTTP webhookAvailabilityAvailableYour connected account’s API permissions and plan apply.
- 01
Create a client webhook
Open the intended client’s Sources area and create a destination for the workflow. Store the address as sensitive configuration rather than displaying it in a shared workflow screenshot.
- 02
Map an HTTP Request node
Configure a POST request with the agreed JSON fields. Use the lead destination for contact events or the number destination for dated numeric values.
- 03
Check success and failure behavior
Test the request, confirm the result in the client workspace and inspect what the workflow does after an error. Make repeated execution safe for the chosen delivery mode.
Know what each
number means.
An HTTP route, not a native node
Use an HTTP Request node in your own n8n workflow. Map its fields to the client’s Monthwrap webhook; a dedicated node is unnecessary.
Your workflow owns delivery logic
The agency controls scheduling, retries and source validation in n8n. A report should only rely on a period after the intended workflow has delivered and its coverage has been checked.
Before you connect
A few useful
answers.
Does this work with self-hosted n8n?
It can use the same HTTP route when the workflow environment can make HTTPS requests to Monthwrap. Network access, scheduling and credentials remain part of your n8n setup.
How do I avoid counting retried events twice?
Use a stable identifier for lead events. For numbers, replacement mode is suitable for complete daily totals; increment mode needs deliberate repeat-handling in your workflow because a repeated addition can change the total.
Can I send a date from an earlier workflow run?
Include the intended date when sending numeric results and preserve the source event time for leads where available. Check the supported fields and reporting period rather than relying on the receiving date as a substitute.
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.