Webhooks
At the heart of an efficient workflow is having the information you need, right when you need it.
With Atarim, webhooks are a vital part of this approach, enabling you to have real-time notifications sent to external services (such as Zapier, Make.com, and many more) whenever specific events happen in Atarim.
For example, if the status of a task is changed in Atarim, you can set up an automated workflow using a webhook to have a notification immediately sent to key people in Asana, Basecamp, Zapier, or whichever platform your team uses.
In this guide we will walk you through setting up and using webhooks with Atarim, focusing primarily on integration with Zapier, as well as Make.com as an alternative.
Understanding Webhooks in Atarim
Webhooks are a way for web applications to send real-time data to other applications when specific events occur.
They work by sending HTTP POST requests to a predefined URL (known as the webhook endpoint) whenever a trigger event happens.
A few examples of the many different events you can have as triggers include:
- New task created
- Task status changed
- New comment added
- New project created
Webhooks are a standard format used by many websites and services, allowing developers to create custom integrations and automate workflows by writing their own code to receive and process these webhook payloads.
Before diving into the technical details of webhooks, it’s crucial to understand that in most cases, you don’t need to configure webhooks manually.
Atarim has done all the hard work for you, and developed first-party integrations for many popular automation platforms, including Zapier and Make.com.
These integrations allow you to connect Atarim with other tools directly, without the need for any manual webhook configuration.
We recommend using these pre-built integrations whenever possible, as they offer:
- Easier setup process
- Pre-configured actions and triggers
- Tested and maintained compatibility
- Potentially better performance and reliability
If you’re looking to automate workflows involving Atarim, check the available integrations first.
Only proceed with manual webhook configuration if you have specific needs that aren’t covered by the existing integrations.
If you do need to work with webhooks directly, let’s explore the two main types of webhooks supported by Atarim: Outgoing Webhooks (Pull) and Incoming Webhooks (Push).
By using both Outgoing and Incoming webhooks, you can create powerful, bi-directional integrations between Atarim and your other tools. This allows for the seamless automation of your workflows, ensuring that your team stays synchronized and productive across all platforms.
1. Outgoing Webhooks (Pull)
Outgoing Webhooks, also known as “Triggers” or “Pull” webhooks, are events that occur within Atarim and send data to external services.
These webhooks are initiated by Atarim when specific events occur, and allow you to send data from Atarim to other services (e.g., Zapier, Make.com) which can trigger actions in external tools based on events in Atarim.
Set Up Outgoing Webhooks in Atarim
Log in to your chosen automation platform, such as Zapier or Make.com, and navigate to the section for creating a new automation or “Zap“.
In the trigger selection step, search for and select “Webhooks” as your trigger app, which will allow you to receive data from external sources such as Atarim.
Within the Webhooks trigger options, you’ll see several event types. Select “Retrieve Poll” as your event type, which allows your automation tool to periodically check for new data from Atarim. This method is ideal for Atarim’s webhook system, ensuring that your automation captures all relevant events.
Next, log in to your Atarim account and navigate to the Dashboard settings. Switch to the integrations tab and look for a section labeled “Webhooks” or “Integrations“, where you’ll find a list of available webhook types.
Enable the specific webhook(s) that correspond to the events you want to trigger your automation, such as “New Task Created” or “Task Status Changed“.
Once you’ve enabled the desired webhook in Atarim, the system will generate a unique URL for that webhook.
Copy this URL from your Atarim Dashboard settings, as you’ll need it for the next step in your automation tool.

Return to your automation tool (Zapier, Make.com, etc.) and locate the “URL” field in the webhook trigger setup. Paste the URL you copied from Atarim into this field.
This URL will be used by your automation tool to retrieve data from Atarim.

In your automation tool’s webhook setup, you’ll likely see a field labeled either “Key” or “Response Key” – enter data into this field. This tells your automation tool to look for the data key in the JSON response from Atarim.
For security purposes, Atarim requires authentication for webhook requests and uses HTTP headers to authenticate each request.
In your automation tool, find the section for adding custom headers to your webhook request. Add a new header with the name webhook-token and set its value to your unique Atarim webhook token, which you can find in your Atarim account settings.

That’s it!
Now you can save the webhook and start using it for creating automations.
2. Incoming Webhooks (Push)
Incoming Webhooks, also known as “Actions” or “Push” webhooks, allow external services to send data and trigger actions within Atarim.
A request can be initiated by external services to push or modify data in Atarim. It is helpful to automate actions within Atarim based on external events
Set Up Incoming Webhooks in Atarim
First, you need to log in to your chosen automation platform, such as Zapier or Make.com, and navigate to the section for creating a new action within your automation workflow.
Once there, look for an option to add a new action step, then search for and select “Webhooks” as your action app.
Within the Webhooks action options, you’ll see several methods for sending data. Select “POST” as your method, as this is the standard way to send data to create resources in Atarim.

Go back to your Atarim account and navigate to the Dashboard settings. Switch to the Integrations tab and scroll down to the webhooks section, where you can find the list of available incoming webhooks.
Enable the specific webhook(s) that correspond to the actions you want to perform in Atarim, such as “Create New Task” or “Update Task Status“.
Once you’ve enabled the desired incoming webhook in Atarim, the system will generate a unique URL for that webhook – copy this URL to your clipboard.

Return to your automation tool and find the “URL” field in the webhook action setup. In this field, paste the URL you copied from Atarim earlier.
Next, look for an option to set either the “Content Type” or “Payload Type“, and select the JSON or Form option, depending on what Atarim expects for the specific webhook you’re using – refer to the following table for the correct type:
Webhook | Payload Type |
New Task | JSON |
New Comment | JSON |
New Note | Form |
New Status Change | JSON |
New Priority Change | JSON |
New Assigned User | Form |
New Tag | JSON |
New Time Entry | Form |

In the “Body” or “Data” section of your webhook action setup, enter the required information for your chosen Atarim action, and format this data as either JSON or form data (matching your chosen payload type), including all necessary fields as specified in the Atarim webhook documentation for your selected action.
The exact steps will vary from tool to tool, but on Zapier, you need to add key value pairs separately.

The following table shows the payload type as well as the sample data for different actions in the Atarim dashboard.
S/N | Actions | Body parameter (Sample Data) | Payload Type |
---|---|---|---|
1 | New Task | {“site”: “demo.wpfeedback.co”,”page”: “Brizy”,”urgency”: “low”,”status”: “open”,”message”: “testing general task creation using webhook actions”,”users”: “Support”} | JSON |
2 | New Comment | {“agency_dashboard_task_url”: “https://app.atarim.io/tasks?website=bzNSancvL1V0dVFyZGxtSW4zNjFSdz09&taskid=SXdKY3poc1dvK3Q1YTlhQ1BlVUVHQT09″,”complete_task”: “no”,”comment_content”: “webhook comment testing”} | JSON |
3 | New Status Change | {“agency_dashboard_task_url”: “https://app.atarim.io/tasks?website=bzNSancvL1V0dVFyZGxtSW4zNjFSdz09&taskid=SXdKY3poc1dvK3Q1YTlhQ1BlVUVHQT09″,”value”: “open”} | JSON |
4 | New Priority Change | {“agency_dashboard_task_url”: “https://app.atarim.io/tasks?website=bzNSancvL1V0dVFyZGxtSW4zNjFSdz09&taskid=SXdKY3poc1dvK3Q1YTlhQ1BlVUVHQT09″,”value”: “critical”} | JSON |
5 | New Tag | {“agency_dashboard_task_url”: “https://app.atarim.io/tasks?website=bzNSancvL1V0dVFyZGxtSW4zNjFSdz09&taskid=SXdKY3poc1dvK3Q1YTlhQ1BlVUVHQT09″,”value”: “testing tag”} | JSON |
6 | Assign User | {“agency_dashboard_task_url”: “https://app.atarim.io/tasks?website=bzNSancvL1V0dVFyZGxtSW4zNjFSdz09&taskid=SXdKY3poc1dvK3Q1YTlhQ1BlVUVHQT09″,”users”: “Tyler”} | |
7 | New Time Entry | {“agency_dashboard_task_url”: “https://app.atarim.io/tasks?website=bzNSancvL1V0dVFyZGxtSW4zNjFSdz09&taskid=SXdKY3poc1dvK3Q1YTlhQ1BlVUVHQT09″,”user”: “Vito Peleg”,”start_time”: “22:07″,”end_time”: “23:07″,”billable”: “yes”,”description”: “Testing add time entry for webhook”,”complete_task”: “yes”} | |
8 | New Note | {“agency_dashboard_task_url”: “https://app.atarim.io/tasks?website=bzNSancvL1V0dVFyZGxtSW4zNjFSdz09&taskid=SXdKY3poc1dvK3Q1YTlhQ1BlVUVHQT09″,”comment_content”: “webhook note tested”,”complete_task”: “no”} |
Next, look for a section in your automation tool where you can add custom headers to your webhook request.
You need to add a new header with the name webhook-token and set its value to your Atarim webhook token, which you can find in your Atarim account settings.
If you do not configure this properly, all your webhook requests to Atarim dashboard will fail.

Finally, for “Wrap Request In Array“, choose “No“, and for “Unflatten“, select “Yes” to ensure that your data is formatted correctly.
Once you have configured all the necessary fields, you can save this webhook and start using it in your automations.
Notes for Actions (Incoming Webhook Body Parameters)
When setting up your webhook action, pay close attention to these parameters:
- complete_task: This parameter specifies whether a task should be marked as complete after the action is performed. It can have one of two values:
- yes: The task will be marked as complete.
- no: The task’s completion status will not be changed.
- billable: This parameter is used for time entries to indicate whether the logged time should be billed to the client. It can have one of two values:
- yes: The time entry will be marked as billable.
- no: The time entry will be marked as non-billable.
- value (for status changes): This parameter is used to specify the new status of a task. It must be one of the following:
- open
- in-progress
- pending-review
- complete
- value (for priority changes): This parameter is used to specify the new priority level of a task. It must be one of the following:
- low
- medium
- high
- critical
Getting Support From Us
Webhooks are a powerful feature in Atarim that can significantly streamline your workflow. By integrating with advanced tools, you can automate repetitive tasks, ensure data consistency across platforms, and improve overall productivity.
If you need help setting up any type of webhook, please do not hesitate to reach out to support@atarim.io and we’ll be happy to help.