Use the OnRamp Zapier Integration to Automate Your Workflows

The OnRamp Zapier Integration (v1.2.2) connects OnRamp directly to over 8,000 apps through Zapier's native app marketplace. Unlike webhook-based automations that only send data out of OnRamp when events happen, the native integration gives you full two-way control: trigger Zaps from OnRamp events and push actions back into OnRamp — creating projects, managing tags, updating data fields, completing tasks, and more.

This article covers everything you need to get started: how to connect, the full list of available triggers and actions, and step-by-step examples for common workflows with tools like Slack, Microsoft Teams, Jira, NetSuite, Snowflake, and Power BI.

Before You Begin

• You need an active Zapier account (Free tier works for basic Zaps; multi-step Zaps require Starter or higher).

• You need an OnRamp API key. To generate one: go to Settings › API in OnRamp and create a new key. Copy it — you'll paste it into Zapier during setup.

• Make sure you have the appropriate OnRamp role (Super Admin or Integrator) to access API settings.

How to Connect OnRamp to Zapier

1. Log into Zapier and click Create Zap.

2. In the trigger or action search, type OnRamp and select it from the results.

3. When prompted to connect your OnRamp account, paste in your API key.

4. Zapier will validate the connection. Once confirmed, you can use OnRamp as a trigger, action, or search in any Zap.

Tip: New customers should use version 1.2.2 of the integration. Previous versions are still supported, but 1.2.2 includes all the latest operations.

OnRamp App vs. Webhooks: Which Should You Use?

OnRamp offers two ways to connect to Zapier. Here's how they differ:

Available Triggers

Triggers are events in OnRamp that start a Zap. All OnRamp triggers fire instantly — there's no polling delay.

Comment Triggers

• Comment Created — fires when a new comment is posted

• Comment Edited — fires when a comment is updated

• Comment Deleted — fires when a comment is removed

• Comment Mention — fires when someone is @mentioned in a comment

• Comment Reply — fires when someone replies to a comment

Project Triggers

• Project Created — fires when a new project is created

• Project Updated — fires when project details change

• Project Completed — fires when a project reaches completion

• Project Archived — fires when a project is archived

• Customer Invited to Project — fires when a customer user is invited

Task & Subtask Triggers

• Task Created / Updated / Completed / Deleted

• Subtask Created / Updated / Completed / Deleted

Module Triggers

• Module Created / Updated / Deleted

Project Note Triggers

• Project Note Created / Updated / Deleted

Available Actions

Actions are things Zapier can do in OnRamp as part of a workflow.

Project & Task Actions

• Create Project — build a fully configured project: choose a playbook, assign an owner, add internal and customer users, set up to 5 task roles, and control invite emails

• Update Project by ID — update an existing project's details

• Add Customer Member to Project — add a customer user to an existing project

• Add Internal User to Project — add an internal team member to a project

• Create Task — add a task to a module with name, description, dates, type, and assignee

• Update a Task — update task details by ID

• Mark a Task as Complete — complete a specific task by ID

• Update Module by ID — rename or update a module

Customer & User Actions

• Create Customer — add a new customer account

• Update Customer by ID — update name, email, or address

• Create a User — create an internal OnRamp user with role, contact info, and job details

• Update a User by ID — modify user info or deactivate accounts

• Create / Update / Delete Customer Note — manage rich-text notes on customer accounts with tag support

Tag Management Actions

• Create Tag / Update Tag / Delete Tag

• Add Tag to Customer, Project, Task, or User

• Remove Tag from Customer, Project, Task, or User

• Find or Create Tag — automatically reuse existing tags or create new ones on the fly

Data Field Actions

• Update Data Field — change a data field's name, description, default value, required status, or currency (USD, CAD, EUR)

• Update Data Field Value — set a specific data field value, with optional auto-creation of missing dropdown options

• Bulk Update Data Field Values — update up to 100 data field values in a single Zap step, with an optional dry-run mode to validate before committing

Available Searches

Searches let you look up existing OnRamp data mid-Zap — useful for mapping IDs, checking status, or building conditional logic.

• Find Customer (by name, email, tag ID, tag UUID) / Find Customer by ID

• Find or Create Customer — searches by name; if no match, creates a new customer automatically

• Find Customer Notes / Find Customer Note by ID

• Find Projects (by name, owner, customer, tag, status, external ID, data field, UUID) / Find Project by ID

• Find Project Members — list all members on a project

• Find Task (by name, overdue status, assignee email, project) / Find Task by ID

• Find Module (by project ID, project UUID) / Find Module by ID

• Find Data Fields (by type: number, monetary, color, link, and more) / Find Data Field by UUID / Find Data Field Values / Find Data Field Value by UUID

• Find Playbooks / Find Statuses / Find Events / Find Webhooks / Find Tag by ID

• Find User (by name, email, tag, customer vs. internal) / Get User Roles

Note: All operations accept both integer IDs and UUIDs, preparing for OnRamp's upcoming transition to UUID-only identifiers.

Example Workflows

1. Send OnRamp Comments and Task Updates to Slack or Microsoft Teams

Goal: Keep your team informed in real time when activity happens in OnRamp.

1. Trigger: OnRamp — Comment Created (or Task Completed, Subtask Completed, etc.)

2. Action: Slack — Send Channel Message (or Microsoft Teams — Send a Message)

3. Map the comment text, project name, and author into the message body.

Variations:

• Use Comment Mention as a trigger to only notify when specific people are @mentioned.

• Use a Zapier Filter step to only send messages for specific projects or customers.

• Send to a project-specific Slack channel by mapping the project name to a channel lookup.

2. Create a Jira Ticket When an OnRamp Task Is Completed

Goal: Automatically hand off completed onboarding tasks to your engineering or implementation team.

1. Trigger: OnRamp — Task Completed

2. (Optional) Filter: Only continue if the task name contains a specific keyword or tag.

3. Action: Jira Software Cloud — Create Issue

4. Map the task name to the Jira issue summary, project name to description, and task owner to assignee.

3. Complete an OnRamp Task When a Jira Issue Is Resolved

Goal: Close the loop — when engineering finishes their work in Jira, automatically mark the corresponding OnRamp task as done.

1. Trigger: Jira Software Cloud — Issue Updated (with a filter for status = "Done")

2. Search: OnRamp — Find Task (match by task name or use a stored ID from the original Zap)

3. Action: OnRamp — Mark a Task as Complete

Pro Tip: When creating the Jira ticket in workflow #2, store the OnRamp Task ID in a Jira custom field. Then in this Zap, pull that ID to look up the right task.

4. Write Project Completion Date to NetSuite for Revenue Recognition

Goal: When an onboarding project completes, automatically update the corresponding NetSuite record so finance can begin revenue recognition.

1. Trigger: OnRamp — Project Completed

2. Search: NetSuite — Find Record (match the OnRamp customer or project to a NetSuite customer/sales order using an external ID or customer name)

3. Action: NetSuite — Update Record — set a custom "Onboarding Completion Date" field to the project's completion timestamp.

Why this matters: Many SaaS companies can't recognize revenue until onboarding is complete. This Zap eliminates the manual handoff between your CS team and finance, ensuring RevRec starts the moment onboarding wraps up.

5. Sync OnRamp Data to Snowflake for Analytics

Goal: Feed onboarding data into your data warehouse for dashboards, cohort analysis, and executive reporting.

1. Trigger: OnRamp — Project Completed (or Task Completed, Project Updated)

2. Action: Snowflake — Insert Row (via the Snowflake Zapier integration or Webhooks by Zapier to a Snowflake ingestion endpoint)

3. Map project name, customer, owner, start date, completion date, and relevant data field values into the target table columns.

Tip: For high-volume ingestion, consider routing OnRamp events to an intermediate staging tool (like Google Sheets or a cloud function) that batch-loads into Snowflake on a schedule.

6. Push OnRamp Data to Power BI for Live Dashboards

Goal: Give leadership a real-time view of onboarding metrics without manual exports.

1. Trigger: OnRamp — Project Completed (or any trigger you want to report on)

2. Action: Microsoft Power BI — Add Rows to a Dataset

3. Map the relevant OnRamp fields (project name, customer, completion date, task counts) to your Power BI dataset columns.

Alternative approach: Use OnRamp's Export feature to generate periodic CSV exports, load them into a shared SharePoint or Google Drive folder, and connect Power BI to that folder as a data source.

7. Tag Customers Based on External Events

Goal: Automatically apply tags in OnRamp based on events from other systems.

1. Trigger: Stripe — New Payment (or any external event)

2. Search: OnRamp — Find Customer (by name or email)

3. Action: OnRamp — Add Tag to Customer

Use this pattern to classify customers as "Enterprise," "At Risk," "Expansion Candidate," or whatever taxonomy your team uses.

8. Bulk-Update Data Fields from a Spreadsheet

Goal: Load data field values into OnRamp in bulk — for instance, importing contract values, renewal dates, or configuration settings from a Google Sheet.

1. Trigger: Google Sheets — New or Updated Spreadsheet Row

2. Action: OnRamp — Bulk Update Data Field Values (up to 100 per step, with dry-run validation)

9. Log OnRamp Activity to Google Sheets or Airtable

Goal: Create a running log of all onboarding activity for audit, reporting, or historical reference.

1. Trigger: OnRamp — Task Completed (or any trigger)

2. Action: Google Sheets — Create Spreadsheet Row (or Airtable — Create Record)

3. Map the task name, project, customer, timestamp, and any other fields you want to track.

Tips & Best Practices

• Use the dry-run option when bulk-updating data fields to validate your changes before they go live.

• Store OnRamp IDs in your other systems (e.g., as a custom field in Jira, HubSpot, or Salesforce) so you can easily look up the right OnRamp record in later Zap steps.

• Use Find or Create Customer instead of separate search-then-create logic — it handles both cases in one step.

• All operations support both integer IDs and UUIDs. If you're building new Zaps, prefer UUIDs for future-proofing.

• Use Zapier Filters to keep your Zaps focused — for example, only trigger on tasks from a specific playbook or customer tag.

• Test with Zapier's built-in testing before turning on a Zap. OnRamp triggers are instant, so changes happen in real time.

What's New in v1.2.2

Version 1.2.2 added 35 new operations, including:

• Create Projects from Zapier with full configuration (playbook, users, task roles, invite control)

• Tag Management — create, update, delete tags and apply/remove them across projects, customers, tasks, and users

• Customer Notes — create, update, and delete notes with rich text (HTML) and tags

• Bulk Update Data Field Values — up to 100 values per step with dry-run validation

• Single-Resource Lookups — look up any customer, project, task, module, user, data field, playbook, or note by ID

• Reference Data Searches — browse tags, playbooks, statuses, events, webhooks, and data field values

• Find or Create Customer — search by name and auto-create if not found

• Smarter Search Filters — filter by email, tag UUID, new data field types (number, monetary, color, link), and more

• UUID Support — all operations accept both integer IDs and UUIDs

Previous versions remain supported. Existing Zaps continue to work without changes.

Related Resources

• Connect OnRamp Webhooks to External Apps with Zapier — for event-driven webhook triggers instead of the native app

• Set Up Webhooks and Authentication in OnRamp — configure webhook endpoints and authentication methods

• OnRamp on Zapier Marketplace — browse pre-built Zap templates and the full trigger/action list