Skip to main content

Connect OnRamp Webhooks to External Apps with Zapier

This guide walks you through creating a webhook trigger in OnRamp and using Zapier to send that data to another app.

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

Use OnRamp webhooks to automate processes by connecting to thousands of external apps using Zapier. Whether you're creating Jira tickets, updating CRM properties, or sending alerts, Zapier helps you route webhook data from OnRamp into actions—without needing to write any code.

This guide walks you through creating a webhook trigger in OnRamp and using Zapier to send that data to another app.


Before You Begin

  • You’ll need a Zapier Starter plan or higher to use Webhooks as a trigger.

  • Make sure you have an active OnRamp account and permission to access Settings > Webhooks.

  • Decide which OnRamp Trigger (e.g., Task Completed, Subtask Answered) should initiate the workflow.


1. Create a Webhook in Zapier

Start by setting up the destination for OnRamp to send data to.

  • Log into Zapier and click Create Zap.

  • For your Trigger, search and select Webhooks by Zapier.

  • Choose the event Catch Hook.

  • Zapier will generate a unique Webhook URLcopy this for use in OnRamp.

  • (Optional) If you only want part of the webhook payload, use the Child Key field (e.g., "contact" from {"contact": {"name": "Mike"}}).


2. Set Up the Webhook in OnRamp

Now you’ll connect OnRamp to Zapier.

  • In OnRamp, go to Settings > Webhooks.

  • Click Create Webhook.

  • Give your webhook a name.

  • Select the OnRamp Trigger that should fire (like Subtask Completed).

  • Paste in the Webhook URL from Zapier.

  • Set Authorization to “No Authorization” if using Zapier.

  • Click Create Webhook.

To test the connection:

  • Complete the relevant action in OnRamp (e.g., finish a task).

  • Zapier should now detect that incoming webhook data.


3. Add Filters in Zapier (Optional)

Narrow down when your Zap should run by adding conditions.

  • Click the + icon and select Filter.

  • Set a rule like:

    • Field = Subtask Name

    • Condition = Contains

    • Value = “Favorite color?”

  • This ensures only relevant data (like a specific task type or name) continues.

📎 Tip: OnRamp webhook payloads include fields like status, subtask name, owner, module name, and more.


4. Choose and Configure Your Action

This is where the real power of Zapier kicks in.

  • Select the app where you want the action to occur (e.g., Jira, Slack, HubSpot).

  • Choose an action event (e.g., Create Ticket, Send Email, Update Property).

  • Use any OnRamp data in the webhook payload to fill in the fields (like using the subtask answer as the Jira title).

Examples:

  • Subtask “Favorite Color” = “Blue” → Create Jira ticket with title: “Blue”.

  • Task Complete → Send a Slack message with the owner and project name.

  • Subtask Answer → Update a CRM field in HubSpot or Salesforce.


Tips & Troubleshooting

  • If your Zap isn't triggering, double-check the webhook is being fired by completing the right action in OnRamp.

  • Use the Zapier Task History to debug and see payload data.

  • You can inspect your webhook payload structure in OnRamp under Settings > Webhooks > Triggers.


Related Resources

Did this answer your question?