Contact events
Send a lead with an email address or phone number and optional name, channel and event time. A stable event identifier helps prevent a repeated delivery from creating another copy of that event.
Inbound webhooks + Monthwrap
Your own data reporting
Send leads and numbers to Monthwrap.
Send leads and named numeric results from a custom system, form backend or automation to a client-specific Monthwrap webhook.
AvailableHTTP webhook
Inside the monthly reportSample data
Northside Systems / Haven Services
From your system to the monthly report
Lead routeContact eventsEmail or phone required
Number routeDated resultsNamed numeric values
RoutingOne clientA dedicated destination address
Source systemCreates a result
PayloadUses agreed fields
Client webhookAccepts the request
Report builderUses the result
Illustrative data flow. A successful request confirms receipt, not the commercial meaning or accuracy of the source result.
Inbound webhooks, at a glance.
- Connect with
- HTTP webhookSend the supported payload to the correct client’s webhook. Configure authentication, date fields and retry handling in your sending system.
- 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 own systems.
Built around your client’s questions
Report an outcome without rebuilding the system behind it.
For agencies connecting internal tools and systems without a dedicated connector.
A client’s operations may live in an internal application, a specialist service or a form backend the agency already maintains. The report does not need to reproduce that system. It needs a defined result, a date, the correct client and enough context to explain what the number means.
Monthwrap webhooks provide destinations for lead events and custom numeric results. Your system prepares the agreed payload, sends it to the client-specific address and checks the response. Use the resulting measures beside connected platform data while keeping source validation, scheduling and business rules in the system that owns them.
Choose the numbers that matter
What Inbound webhooks
brings to the report.
Leads and custom numeric results from your own systems. Choose the relevant figures, add comparisons where the data supports them, and explain what changed.
Named daily numbers
Send a date and one or more numeric values with readable labels. These become custom measures the agency can use in reporting; keep labels and units consistent over time.
Replacement totals
Use replacement mode when sending the complete value for a day. This suits nightly summaries and corrections because the new value takes the place of the earlier daily total.
Incremental results
Use add mode when each accepted request represents another count or amount. The sender must control retries and repeated execution so an event is not unintentionally added twice.
For your next client report
A custom booking system
Send the confirmed booking result after the system has accepted it. Keep requests, confirmed bookings and completed appointments as separate measures rather than using one unclear conversion label.
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 Inbound webhooks
to the right client.
Send the supported payload to the correct client’s webhook. Configure authentication, date fields and retry handling in your sending system.
Connection methodHTTP webhookAvailabilityAvailableYour connected account’s API permissions and plan apply.
- 01
Create the destination in Sources
Choose the correct client, add a webhook and name it for the sending system. Keep the address private because possession of it allows data submission for that client.
- 02
Choose the payload and route
Use the lead route for contact records or the number route for dated values. Agree the source fields, labels, event identifiers and replacement or increment behavior before sending.
- 03
Verify a small test
Send an agreed test, inspect the response and confirm the result in Monthwrap. Add error handling and respect retry instructions before using the sender for recurring reporting.
Know what each
number means.
A receipt is not data validation
An accepted request means the payload was received in a supported form. The sending system and agency still need to verify whether the underlying result is accurate, complete and correctly defined.
Addresses are sensitive
Treat a client webhook address like a credential. Do not put it in public website code, screenshots or client reports. Revoke and replace a destination if it is exposed.
Before you connect
A few useful
answers.
Can a webhook send both leads and numeric results?
The client destination has separate lead and number routes. Use the appropriate payload for each. A lead record and a numeric count can describe related activity, but the report should not count them as two separate business outcomes.
What happens when a request is retried?
A lead event with the same identifier is skipped. Numeric replacement sets the day’s value again, while an additional increment can add to it again. Choose the delivery mode and retry behavior deliberately.
Is this a replacement for every native integration?
It is an option when your system can produce the expected payload. Native connections can provide their own platform-specific reporting behavior; a webhook only knows the fields your sender prepares.
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.