1. What are Webhooks?
Webhooks are an efficient, automated way to receive real-time updates whenever specific events occur in Modjo.
Instead of manually checking for updates, Modjo sends the information directly to your connected tools as soon as an event is triggered.
With Webhooks, you can seamlessly integrate Modjo with your existing tools, saving time, improving collaboration, and keeping data synchronized across platforms.
This feature is particularly useful for:
Syncing data: Keep your systems up-to-date in real-time.
Automating workflows: Eliminate repetitive tasks by automating key processes.
Integrating Modjo with third-party tools: Enhance productivity by connecting Modjo to tools like Slack, Zapier, or internal systems.
2. How to use Modjo Webhooks?
Modjo Webhooks offer flexible ways to customize your workflows and enhance your integrations. Here are some practical examples:
Receive all your summaries in Slack: Set up a Webhook to receive a notification in Slack whenever a call summary becomes available. This centralizes key information directly in your preferred collaborative space. Refer to the Slack documentation for guidance on setting this up.
Integrate your summaries into an internal tool: Webhooks can automatically transfer Modjo call summaries to internal tools, allowing you to centralize your data seamlessly.
Automate your processes with Zapier or Make: Create automations triggered by the arrival of a Modjo summary. For example, you can configure an action to generate a task or a notification for each new summary.
3. How to set p Webhooks
🚨 Prerequisites : Before creating a Webhook, you must have Administrator or Manager permissions.
Steps to Create a Webhook
Click "Create Webhook" and enter the URL where you want to receive Webhook notifications.
Once created, you will receive a unique security token. This token will be used to verify incoming Webhook requests and ensure they are genuinely sent by Modjo.
4. Securing your Webhook endpoint
Since Webhooks send data to the specified URL, it’s crucial to carefully select and secure the endpoint that will receive this information.
Best practices for Webhook security :
Use HTTPS: Always provide a secure HTTPS endpoint to encrypt data in transit.
Ensure the URL is accessible: The system receiving the Webhook must be reachable from the internet. If you’re testing locally, consider using tools like ngrok to expose your local server.
Do not expose sensitive endpoints: The Webhook URL should be dedicated to receiving Webhooks and should not be accessible by unauthorized users.
Validate incoming requests: You should verify the Webhook signature using the security token provided when you created the Webhook. This ensures the requests are truly coming from Modjo.
Be aware of the data being sent: Webhooks may contain sensitive business data, so avoid using publicly accessible endpoints where unauthorized parties might intercept the information.
5. Managing Webhooks
You can edit or delete your Webhooks at any time from the Webhook settings page.
If you no longer need a Webhook, we strongly recommend deleting it to prevent unnecessary requests.
If you suspect unauthorized access, you should recreate the Webhook to generate a new security token.
For details on:
Different Webhook events
Handling Webhook requests
Verifying their authenticity
Please refer to the Modjo API Documentation.