Integration guides

These are patterns that work well with WRMS Pro webhooks. They describe your side of the integration; WRMS Pro's side is the same for all of them.

A reliable receiverCopy Anchor Link

This keeps you well inside the 10-second limit and makes failures in your downstream systems your problem to retry, rather than WRMS Pro's.

Keep a copy of records in stepCopy Anchor Link

Webhooks tell you that a record changed and which one (entity, entityId). Because the data object is not yet documented field by field, design your sync so it:

• keys everything by organizationId + entityId;
• treats *.delete events as the signal to remove or archive;
• tolerates missing or extra fields in data.

Notify your team elsewhereCopy Anchor Link

Subscribe a webhook to quote.status and payment.create, and forward a short message to your team chat when a quote is accepted or a payment arrives. Filter on the event name before forwarding.

Automation toolsCopy Anchor Link

Tools that can receive a webhook (a "catch hook" or "webhook trigger") can be pointed at WRMS Pro directly. Most cannot verify the signature themselves; if yours cannot, put a small receiver in front of it that verifies and then forwards.

TestingCopy Anchor Link

• Use Send test to send ping.test at any time.
• Watch Deliveries in Settings → Webhooks for status codes and responses.
• Use a separate webhook for your test endpoint, and delete it when you are finished.