A web-hook is a simple way to let one application talk to another in real time. Instead of constantly checking if something has changed, an app sends a signal to Oppz.ai as soon as an event happens. That signal tells your flow to start running.

Web-hooks use a special URL (called an endpoint) to send and receive information, usually in JSON format.

⚙️ How Web-hooks Work

🔹 As a Trigger

• You can create a web-hook endpoint in Oppz.ai.
• When another system (like a CRM, form, or e-commerce app) sends data to this endpoint, it automatically triggers your flow.
• Oppz.ai instantly acknowledges the request, then processes the data in the background for speed and reliability.

The image below highlights where the Webhook option is located. Use it as a reference when setting up your workflow:

✅ Best Practices for Web-hooks

• 🔒 Secure Your Data → Always validate incoming payloads to confirm they are from a trusted source.
• ⚡ Respond Quickly → Return a 200 OK immediately. Do your actual processing in the background to avoid timeouts.
• 🛡️ Avoid Duplicates → Use duplicate-safety keys so even if a web-hook is sent multiple times (due to retries), it only gets processed once.
• 📑 Keep Logs → Log every incoming and outgoing web-hook. This makes troubleshooting much easier.

⚠️ Important Notes

• Protect Your Endpoints → Web-hook URLs are public, so secure them using:
  • Signed requests
  • IP allowlists (accept requests only from trusted IPs)
• Know the Limits → Be mindful of:
  • Payload size → Large data may need batching.
  • Rate limits → High-volume systems should send data in groups instead of one item at a time.