Skip to main content

Set Up Webhooks and Authentication in OnRamp

Webhooks let you automatically send information from OnRamp to another system when something happens.

Paul Holder avatar
Written by Paul Holder
Updated over a month ago

Webhooks let you automatically send information from OnRamp to another system when something happens—like when a task is completed or a project is updated. Use this feature to trigger external workflows, send data to tools like Jira or Slack, or build powerful automations using tools like Zapier or Make.

Webhooks can also include authentication so your receiving system knows the call is secure.


Before You Begin

Make sure you:

  • Have access to Settings > Webhooks (available to Super Admins and Integrators)

  • Know the URL of the endpoint you want to send data to

  • Understand what trigger you want to use (e.g., when a task is completed)

If you're using Zapier, we recommend reviewing the Webhooks via Zapier article first.


1. Go to Webhooks in Settings

  • Head to Settings > Webhooks in the left navigation under Advanced.

2. Click Create Webhook

  • You'll land on the Webhooks tab. Click Create Webhook.

3. Enter Your Webhook Details

  • Webhook Name – Something meaningful like Create Jira Ticket on Task Completion

  • Trigger – Choose the event in OnRamp that should trigger this webhook (see full list below)

  • Webhook URL – The destination where the webhook will send data

  • Authorization – Select how this webhook authenticates:

    • No Authorization – For tools like Zapier

    • API Key / Token – For internal or secured endpoints

4. Click Create Webhook

Once everything looks good, click Create Webhook to save and activate it.


Available OnRamp Triggers

These are the actions in OnRamp that can launch a webhook. You can view them in the Triggers tab under Settings > Webhooks to see data schemas.

  • Customer Invited to Project

  • Module Created / Deleted / Updated

  • Project Created / Archived / Completed

  • Project Details Updated

  • Project Note Created / Deleted / Updated

  • Task Created / Completed / Deleted / Updated

  • Subtask Created / Completed / Deleted / Updated

  • Task Help Requested

Each trigger sends structured data you can use in your destination system.


Example Use Case

Here’s how a webhook works when paired with Zapier:

  1. OnRamp Trigger: A customer completes a task.

  2. Zapier receives the webhook

  3. Webhook Action: A Jira ticket is created using the task’s data.

🎥 See image example above


Tips & Troubleshooting

  • Testing your webhook: Use a service like Webhook.site to inspect your payloads.

  • Authentication not working? Double-check that your API key is correctly formatted in the header or query string, depending on your endpoint.

  • Webhook not firing? Make sure the trigger condition is actually happening (e.g., “Task Completed” requires the task to be marked complete in the UI or automation).


Did this answer your question?