Resources · Zapier integration

OnRamp Zapier integrationAutomate OnRamp with Zapier.

The OnRamp Zapier integration gives you 28 triggers, 93 actions and 46 searches. Every trigger is instant, OnRamp runs on the free plan, and each operation below says what it does, what it costs and where it trips people up.

See the 167 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the OnRamp Zapier integration actually does

OnRamp is a customer onboarding and collaboration tool, and Zapier is the bridge that moves its events into other apps and back. You build a Zap (one automation: a trigger that starts it, then one or more actions that run each time). With OnRamp, the trigger can be almost any change on a project, a task, a module, a note or a comment.

Three results people usually build first. A kickoff that sets itself up: Project Created fires, Add Project Member puts the right people on it, and Add Note to Project leaves the welcome brief. A customer record that stays complete: Customer Invited to Project fires, and Create Customer Note logs who joined and when the invitation went out. A tidy end of project: Project Completed fires, then Archive Project and Add Tag to Project close the file without anyone opening OnRamp.

The good news for a free-plan user: all 28 OnRamp triggers are instant, so the plan's waiting time never applies. The app reports each event to Zapier itself, and the Zap starts right away.

What Zapier does not do here. It does not import the projects, tasks or notes you already have: a Zap only reacts to what happens after you switch it on. It cannot undo a delete, and OnRamp marks nearly all of its delete and remove actions as irreversible. It also has no say over which fields OnRamp asks for: most actions want the ID of a project, a customer, a task or a tag, so plan where that ID comes from before you build.

If you are still choosing a tool, the n8n vs Zapier and Make vs Zapier comparisons are there.

Vocabulary

Zapier words you will meet on this page

Eight terms, each in one plain line. They come back on every block below.

Zap
Your automation on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in OnRamp that starts the Zap, like a task being completed. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that creates, updates, moves or deletes something for you in an app.
Task
The unit Zapier bills. One action your Zap completes successfully equals one task, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when the incoming data meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something already in an app, such as a customer or a tag, so the next steps can use what it found.
Connection
Your OnRamp account linked to Zapier once, then reused by every step of every Zap that touches OnRamp.
Cost

What an OnRamp Zap really costs

The trigger never costs a task, and neither does Zapier listening for events. You pay for actions that succeed, one task each.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • OnRamp triggers28 instant, 0 polling

A Zap with three OnRamp actions spends three tasks per run, while an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a second action, a filter or a search, and it becomes a multi-step Zap that needs a paid plan. OnRamp itself is not reserved to paid plans. The interval grid below only matters for polling triggers, and OnRamp has none.

Connect

Connect your OnRamp account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an OnRamp account first, plus access to any project or customer you do not own and want the Zap to touch.

  2. 02

    Pick OnRamp

    Type OnRamp in the search box of the dialog, select it in the results, then click Add connection. Zapier opens a new tab where the OnRamp side of the link happens.

  3. 03

    Sign in and grant access

    Log in to OnRamp in that tab and allow Zapier to use the account. The connection is then saved in Zapier, and every OnRamp step in every Zap you build reuses it.

First Zap

Your first OnRamp Zap, step by step

GoalEvery new project gets its account manager added and a welcome note posted.

  1. 01

    Build the trigger

    Start a new Zap, pick OnRamp as the app and Project Created as the event, then choose your OnRamp connection. A lightning bolt shows this trigger is instant.

  2. 02

    Test it on a real project

    Run the trigger test. Zapier brings back the three most recent projects from your account, so pick one and use it to map every field that follows.

  3. 03

    Add the member

    Add the action Add Project Member. Map the Project ID from the trigger, then set the User ID of the account manager. Both accept a plain number or a UUID.

  4. 04

    Post the welcome note

    Add a second action, Add Note to Project. Map the same Project ID and write the Note Detail; that field takes HTML, so a short formatted checklist works.

  5. 05

    Test, then publish

    Test each action once and read what OnRamp sent back. Then publish to switch the Zap on. With two actions it is a multi-step Zap, so it needs a paid plan.

Triggers

OnRamp triggers: the 28 events that can start a Zap

28 events start a Zap when something happens in OnRamp, and 28 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Comment Deleted

Instant trigger

In Zapier“Triggers when a comment is deleted.”

Starts your Zap when someone removes a comment in OnRamp. The run carries the comment that vanished, which is handy when a conversation thread is your audit trail.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a copy of deleted customer comments in a log sheet so account managers can still see what was said before it disappeared.
Watch out
the comment is already gone on the OnRamp side, so a later step cannot look it up with Find Comment; store what the trigger gives you.
2

Comment Mention

Instant trigger

In Zapier“Comment when a mention is included in a comment.”

Fires whenever a comment includes a mention of someone. This is the trigger that turns an @-tag inside OnRamp into a ping wherever the person actually reads messages.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
forward mentions to a chat channel for a customer success manager who lives in Slack rather than in the OnRamp inbox.
Watch out
a comment that mentions three people is still one event, so decide in the next step who gets notified.
3

Comment Created

Instant trigger

In Zapier“Triggers when a new comment is created.”

Each new comment written in OnRamp sets this Zap off. It is the broadest comment trigger, catching internal remarks and customer replies alike.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
copy every comment on onboarding tasks into your support desk so the whole conversation sits next to the ticket history.
Watch out
if the same Zap uses Add Comment to Task, it writes a comment that sets itself off again, an endless loop that eats tasks.
4

Comment Reply

Instant trigger

In Zapier“Triggers when a user replies to a comment.”

Here the event is narrower: a user answering an existing comment. Top-level comments are ignored, so you only hear about conversations that are already going.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
alert the person who asked a question when the customer finally answers it, without flooding them with every new remark on the project.
Watch out
pair it with Comment Created only if you really want both, or the same exchange may notify twice.
5

Comment Edited

Instant trigger

In Zapier“Triggers when a comment is edited.”

Somebody changes the text of a comment after posting it, and this trigger reacts. The run reflects the comment as it reads after the edit.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when comments carry approvals or sign-offs, record each edit in a spreadsheet so a changed answer never goes unnoticed.
Watch out
a Zap that runs Update Comment on the same comment edits it again and loops, so never write back to the comment you are watching.
6

Project Created

Instant trigger

In Zapier“Triggers when a new project is created.”

A brand-new project appearing in OnRamp is the event here. It is the natural starting point of most onboarding automations, since everything else hangs off the project.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
open a matching deal stage in your CRM, create a shared folder, or staff the project with Add Project Member when sales hands it over.
Watch out
projects created by the Zap's own Create Project action fire this trigger too, so keep those two in separate Zaps.
7

Customer Invited to Project

Instant trigger

In Zapier“Triggers when a Customer is invited to a Project.”

When a customer contact receives an invitation to a project, Zapier hears about it. This is the moment the customer side of the onboarding officially opens.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
send a personal welcome email from your own mailbox, or log the invite with Create Customer Note so the account history stays complete.
Watch out
the event is the invitation, not the acceptance; a customer who never logs in still started the Zap.
8

Customer Note Created

Instant trigger

In Zapier“Triggers when a note is added to a customer account.”

Notes added to a customer account start this Zap. Notes are where teams leave context about the client, so this trigger moves that context out of OnRamp.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
mirror each account note into the matching CRM record so sales sees what onboarding learned about the customer.
Watch out
a Zap that also runs Create Customer Note on the same account will trigger itself; send notes outward only.
9

Customer Note Deleted

Instant trigger

In Zapier“Triggers when a customer account note is deleted.”

Removing a note from a customer account is the signal. Use it as a safety net when notes matter for compliance or handovers.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
post a short alert in the account team's channel naming the customer, so nobody wonders later where an agreed detail went.
Watch out
Delete Customer Note is irreversible on OnRamp's side, and so is a manual delete; the Zap can report it but cannot bring the note back.
10

Customer Note Updated

Instant trigger

In Zapier“Triggers when a customer account note is updated.”

This one watches edits to existing customer account notes. Each saved change sends the updated note to your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a CRM copy of a note in step with OnRamp, overwriting it each time the onboarding team refines its account summary.
Watch out
several quick saves mean several runs, and each successful action in them is a task, so check how often your team edits notes.
11

Module Created

Instant trigger

In Zapier“Triggers when a new project module is created.”

OnRamp groups project work into modules, and this trigger fires when a new one is added to a project. It tells you the shape of the plan is changing.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
tag every new module with Add Tag to Module so reporting by phase stays consistent across projects built by different people.
Watch out
modules added by Create Module in another Zap also count, which is fine unless that Zap is this one.
12

Module Deleted

Instant trigger

In Zapier“Triggers when a project module is deleted.”

A project module being removed sets this off. Since a module usually holds several tasks, a delete here can wipe a chunk of the plan at once.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
warn the project owner in chat whenever a module disappears, so an accidental delete is caught the same day.
Watch out
the module no longer exists, so Find Module by ID will come back empty in a later step; use what the trigger delivered.
13

Module Updated

Instant trigger

In Zapier“Triggers when a project module is updated.”

Changes to a project module, such as a rename, start this Zap. It is the trigger for keeping outside trackers aligned with the current plan.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
update the matching row in a delivery dashboard so leadership reads the same phase names the team works with.
Watch out
Update Module by ID in the same Zap would edit the module and fire this trigger again, so keep write-backs in another Zap.
14

Project Archived

Instant trigger

In Zapier“Triggers when a project is archived.”

Archiving a project is the event. For most teams that means the onboarding is closed for good, which makes it a clean point to wrap things up elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
move the related CRM deal to its final stage or close the shared channel once OnRamp puts the project away.
Watch out
unarchiving fires a different trigger, Project Unarchived, so plan the reverse path if your team ever reopens projects.
15

Project Completed

Instant trigger

In Zapier“Triggers when a project is completed.”

Fires when a project is marked complete. Completion is usually the milestone your finance or success team is waiting for.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
start the handover to the account team, send a satisfaction survey, or ask billing to issue the first recurring invoice.
Watch out
Uncomplete Project can reopen it, and completing it again fires this trigger again, so make sure a second run does no harm.
16

Project Note Created

Instant trigger

In Zapier“Triggers when a project note is created.”

New notes on a project kick off this Zap. Project notes tend to hold meeting summaries and decisions, the details people later search for.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
archive every project note into a shared document so the delivery team has one searchable history per client.
Watch out
Add Note to Project in the same Zap writes a note that restarts it; that loop is the classic way to burn the 100 free tasks.
17

Project Note Deleted

Instant trigger

In Zapier“Triggers when a project note is deleted.”

Triggered by a project note being removed. It gives you a trace of what was there, which OnRamp no longer keeps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
append a line to an audit sheet with the project and the time of the delete, useful when several people edit the same workspace.
Watch out
the delete cannot be undone from Zapier; at best your Zap keeps a record of it.
18

Project Note Updated

Instant trigger

In Zapier“Triggers when a project note is updated.”

Edits to an existing project note are what this trigger listens for. Each save sends the new version.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
refresh a client-facing status page every time the project lead rewrites the weekly summary note in OnRamp.
Watch out
Update Project Note on the same note would loop back here, so keep any rewrite in a Zap with a different trigger.
19

Project Unarchived

Instant trigger

In Zapier“Triggers when an archived project is unarchived.”

An archived project coming back to life starts this Zap. It is rare, which is exactly why it is worth hearing about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
reopen the CRM deal or alert the account owner that onboarding work has resumed on a client they thought was done.
Watch out
anything your Project Archived Zap closed elsewhere stays closed unless this Zap reopens it explicitly.
20

Subtask Completed

Instant trigger

In Zapier“Triggers when a subtask is completed.”

Checking off a subtask is enough to start this Zap. It is the finest-grained progress signal OnRamp offers.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
track checklist progress in a spreadsheet when your onboarding steps are broken into many small items a customer ticks off.
Watch out
a task with many subtasks means many runs, and each successful action in each run counts as a task.
21

Subtask Created

Instant trigger

In Zapier“Triggers when a subtask is created.”

Reacts to a new subtask being added under a task. Useful when subtasks represent requests or deliverables you want tracked outside OnRamp.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
push each new subtask into your team's to-do tool so the person assigned sees it in the list they already check.
Watch out
subtasks that your own Create Subtask action adds will fire it too; keep that action out of this Zap.
22

Subtask Deleted

Instant trigger

In Zapier“Triggers when a subtask is deleted.”

Removal of a subtask is the event. It is mostly used to keep a mirrored list clean.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
delete or strike through the matching item in an outside checklist so the two lists never drift apart.
Watch out
the Zap needs a way to find the mirrored item, so store the OnRamp subtask ID in that other tool when you first create it.
23

Subtask Updated

Instant trigger

In Zapier“Triggers when a subtask is updated.”

Any change to a subtask, including the answer a customer fills in, starts this Zap. That makes it the trigger for collecting responses.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when subtasks hold questionnaire answers, copy each new answer into the customer's CRM record.
Watch out
Update Subtask / Set Answer in the same Zap writes to the subtask and restarts it; that is a loop.
24

Task Completed

Instant trigger

In Zapier“Triggers when a task is marked as completed.”

A task marked as completed is the signal here. For milestones like a signed contract or a finished integration, this is the event that matters.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
notify the next team in line, for instance support, when the go-live task in a project gets ticked.
Watch out
every completed task in every project fires it; on a free plan you cannot add a filter, so pick a more specific trigger if you can.
25

Task Created

Instant trigger

In Zapier“Triggers when a new task is created.”

New tasks in OnRamp start this Zap. It catches tasks added by hand or by another Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
create a matching card in an internal board for tasks your engineers handle, so they never need an OnRamp seat.
Watch out
a bulk import or a migration can create a batch of tasks at once, and a large batch may be held back by Zapier's flood protection.
26

Task Deleted

Instant trigger

In Zapier“Triggers when a task is removed from a project.”

Triggers once a task is removed from a project. It is the counterpart you need if you mirror tasks anywhere else.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
archive the matching card on your engineering board so nobody keeps working on something the customer no longer needs.
Watch out
Delete Task is irreversible, and the task cannot be fetched afterwards; rely on the trigger data only.
27

Task Updated

Instant trigger

In Zapier“Triggers when a project task is updated.”

Fires on edits to a project task, such as a new due date or a changed owner.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep due dates in a shared calendar aligned with OnRamp, so customers and staff see the same plan.
Watch out
never write back with Update a Task in the same Zap, or the edit starts it all over again.
28

Project Updated

Instant trigger

In Zapier“Triggers when a Project's details are updated.”

Edits to a project's details start this Zap. Think renamed projects, new owners or shifted dates.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
sync project details to the CRM deal so the sales owner sees the live target date without asking the onboarding lead.
Watch out
Update Project by ID or Add Tag to Project in the same Zap may count as a change and restart it; test one run before publishing.
Actions

OnRamp actions: what your Zap can do

OnRamp gives you 93 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Task to Library Module

Action

In Zapier“Adds a task to a library module.”

Fills a library module with a task, from the module UUID and a task name.

When to use it
keep a reusable phase current as your process document evolves.
Watch out
the module UUID accepts a plain number too, so mapping from Find Library Modules works either way.
2

Add Module to Playbook

Action

In Zapier“Adds a module to a playbook.”

Grows a playbook with a new module, given the playbook UUID and a module name.

When to use it
build out a draft playbook from a list kept in a spreadsheet.
Watch out
the new module starts empty; fill it with Add Task to Playbook Module.
3

Add Project Member

Action

In Zapier“Adds a member to an existing project.”

Puts an existing user on an existing project, from the project ID and the user ID.

When to use it
staff each new project with its account manager the moment it is created.
Watch out
the person must already be an OnRamp user, so chain Create a User first for newcomers.
4

Add Tag to Customer

Action

In Zapier“Adds a tag to a customer.”

Labels a customer account with an existing tag. Both the customer ID and the tag ID are required.

When to use it
mark customers by plan or segment when your billing tool reports an upgrade.
Watch out
it needs the tag's ID, not its name, so add Find Tags in front when you only know the label.
5

Add Tag to Module

Action

In Zapier“Adds a tag to a module.”

Applies a tag to one module, using the module ID and the tag ID.

When to use it
flag modules that depend on a partner, so they show up together in reviews.
Watch out
both IDs accept a number or a UUID, which saves a conversion step.
6

Add Tag to Project

Action

In Zapier“Adds a tag to a project.”

Tags a whole project. Give it the project ID and the tag ID.

When to use it
label projects by region or by sales rep as they arrive from the CRM.
Watch out
if this runs from Project Updated, test whether the new tag counts as an update before publishing.
7

Add Tag to Task

Action

In Zapier“Adds a tag to a task.”

Puts a tag on a single task, from the task ID and the tag ID.

When to use it
mark tasks that are blocked on the customer when a status changes elsewhere.
Watch out
starting from Task Updated may loop if tagging counts as a task edit.
8

Add Tag to User

Action

In Zapier“Adds a tag to a user.”

Tags a user, staff or customer, with a user ID and a tag ID.

When to use it
mark customer contacts who are decision makers once your CRM flags them.
Watch out
the user ID can be a number or a UUID; Find User by ID returns it.
9

Add Task to Playbook Module

Action

In Zapier“Adds a task to a module within a playbook.”

Places a task inside a module of a playbook. Playbook UUID, module UUID and task name are required.

When to use it
fill a template module task by task from an approved checklist.
Watch out
Find Playbook Modules gives you the module UUIDs of that playbook.
10

Bulk Update Data Field Values

Action

In Zapier“Bulk updates up to 100 data field values in one request.”

Updates up to 100 data field values in one request, each given by its value UUID and new value. A dry-run switch checks without saving.

When to use it
an export from your data warehouse refreshes many fields at once.
Watch out
run it once with dry run on before trusting real data.
11

Add Comment to Task

Action

In Zapier“Adds a new comment to a task.”

Writes a new comment on a task. You pass the task ID and the message.

When to use it
post a status update from another tool, like a shipped order or a passed test, where the customer will read it.
Watch out
a Zap started by Comment Created that also runs this action loops forever.
12

Create Customer

Action

In Zapier“Creates a new customer.”

Adds a new customer account to OnRamp. You supply a name, an email address and a mailing address, all three required.

When to use it
a deal closes in your CRM and the customer should exist in OnRamp before the kickoff call.
Watch out
to avoid duplicates, Find Customer with its find-or-create option is often the safer choice.
14

Create Customer Note

Action

In Zapier“Creates a new note for a customer.”

Leaves a note on a customer account. Only the customer ID and a note title are required.

When to use it
record a call summary from your meeting recorder on the right account.
Watch out
the customer ID accepts both a number and a UUID; if you only have a name, add Find Customer before this step.
15

Add Resource to Customer

Action

In Zapier“Adds a new resource to a customer.”

Links a resource to a customer account. Customer ID, resource type, title and URL are all mandatory.

When to use it
share a contract or a training video with the customer once your document tool generates it.
Watch out
a missing URL stops the step, so test with a record that really has one.
16

Create Data Field

Action

In Zapier“Creates a new data field in the system.”

Defines a new custom data field. Name, field type and object type are required; optional switches say whether it is required and applied on creation.

When to use it
roll out a new field across accounts without setting it up by hand.
Watch out
object type uses the same choices as the Find Data Fields search.
17

Create Data Field Option

Action

In Zapier“Creates a new option for a dropdown or multi_select data field.”

Adds a choice to a dropdown or multi_select data field, from the field UUID and the option value.

When to use it
a new value appears in your CRM picklist and OnRamp should offer it too.
Watch out
it fails on any other field type, so point it only at dropdown or multi_select fields.
18

Create Library Module

Action

In Zapier“Creates a library module.”

Adds a module to the library, the store of reusable building blocks, from a module name.

When to use it
standardise a recurring phase, such as data migration, so every project can pull it in.
Watch out
it starts empty; follow with Add Task to Library Module to fill it.
19

Create Library Task

Action

In Zapier“Creates a library task.”

Saves a reusable task to the library, with only a task name required.

When to use it
capture a recurring step, like a security review, once, then reuse it across playbooks.
Watch out
a library task is not attached to any project until someone adds it to a module.
20

Create Module

Action

In Zapier“Creates a module in the system.”

Inserts a new module into an existing project. Give it the project ID and a module name.

When to use it
a customer buys an add-on and the project needs an extra phase for it.
Watch out
the project ID can be a plain number or a UUID, so map it straight from a trigger or a Find Project step.
21

Create Playbook

Action

In Zapier“Creates a new playbook.”

Starts a new playbook, OnRamp's reusable project template, from just a name.

When to use it
spin up a draft template for each new offer your team launches, ready to be filled in.
Watch out
the playbook still needs modules and tasks, and Publish Playbook before teams can use it.
22

Create Project

Action

In Zapier“Creates a new project with full configuration including playbook, users, task roles, and invite options.”

Opens a full project in one step, with playbook, users, task roles and invite settings available. A name, a start date and a project owner are mandatory.

When to use it
kick off onboarding automatically when a contract is signed.
Watch out
the start date expects MM/DD/YYYY, and the owner must be a UUID or an email of an existing user.
24

Add Note to Project

Action

In Zapier“Adds a new note to a project.”

Attaches a note to a project, with formatting: the note detail accepts HTML. Project ID and note detail are required.

When to use it
drop a welcome brief or a kickoff agenda the moment a project starts.
Watch out
keep it away from the Project Note Created trigger in the same Zap.
25

Add Resource to Project

Action

In Zapier“Adds a new resource to a project.”

Same idea at project level: a typed resource with a title and a URL, attached to one project.

When to use it
make a freshly created shared folder visible inside the onboarding project.
Watch out
four fields are required, and the resource type must match what OnRamp offers.
26

Create Subtask

Action

In Zapier“Creates a new subtask on a task.”

Breaks a task down by adding a subtask under it, from a task ID and a subtask name.

When to use it
split a big task into a checklist when a new requirement lands from your ticketing tool.
Watch out
do not run it from the Subtask Created trigger, or each new subtask creates another one.
27

Create Tag

Action

In Zapier“Creates a new tag.”

Makes a new tag in OnRamp from a tag name.

When to use it
a new product line or region appears and you want a label ready before any project needs it.
Watch out
creating a tag that already exists may give you a duplicate; Find Tags with find-or-create avoids that.
28

Create Task

Action

In Zapier“Creates a task in the system.”

Puts a new task inside a module. It needs the module's UUID, a task name and a task type.

When to use it
a form submission from the customer should become a to-do for your team inside the right module.
Watch out
the module UUID has to come from somewhere; Find Module by ID or a Module Created trigger provides it.
29

Delete Comment

Action

In Zapier“Deletes a comment. This action is irreversible.”

Erases a comment for good, from its comment UUID. Unlike Update Comment, nothing of the original text remains afterwards.

When to use it
remove automated comments that a broken Zap posted by mistake.
Watch out
irreversible, and integer comment IDs are deprecated; pass the UUID.
31

Delete Customer Note

Action

In Zapier“Deletes a customer note. This action is irreversible.”

Removes a note from a customer account, with the customer ID and the note ID. The note disappears from the account timeline for every user at once.

When to use it
purge notes tied to a data-deletion request.
Watch out
there is no undo; test on a dummy customer.
32

Delete Customer Resource

Action

In Zapier“Deletes a customer resource. This action is irreversible.”

Takes a resource off a customer account, from the customer ID and the resource UUID. The link vanishes from the customer view, while the file it pointed to stays wherever it lives.

When to use it
withdraw an expired offer document from every account that had it.
Watch out
OnRamp cannot restore it afterwards.
33

Remove Data Field Option

Action

In Zapier“Removes an option from a dropdown or multi_select data field.”

Drops a choice from a dropdown or multi_select field, with the field UUID and the option ID.

When to use it
a product is retired and its option must disappear from forms.
Watch out
check which records still use that option before removing it.
34

Delete Library Module Task

Action

In Zapier“Deletes a task from a library module. This action is irreversible.”

Takes a task out of a library module, using the module UUID and the task UUID.

When to use it
trim a standard phase after a process review.
Watch out
permanent; Archive Library Task is the gentler option for standalone tasks.
35

Delete Module

Action

In Zapier“Deletes a module. This action is irreversible.”

Deletes a whole project module, from its module ID. A module groups tasks, so a single run can remove a whole phase of a project.

When to use it
remove a phase the customer opted out of.
Watch out
no undo, and it fires Module Deleted in any Zap watching it.
36

Delete Playbook Task

Action

In Zapier“Deletes a task from a playbook. This action is irreversible.”

Strips a task out of a playbook, with the playbook UUID and the task UUID. It changes the template, not a running project.

When to use it
strip an obsolete step from a template.
Watch out
irreversible; Find Playbook Tasks confirms the right UUID.
38

Delete Project Note

Action

In Zapier“Deletes a project note. This action is irreversible.”

Deletes a project note, given only its note UUID. Unlike the customer version, this one asks for nothing but the note UUID.

When to use it
clean out temporary notes that another Zap created during setup.
Watch out
irreversible, and it fires Project Note Deleted.
39

Delete Project Resource

Action

In Zapier“Deletes a project resource. This action is irreversible.”

Removes a resource from a project, using the project ID and the resource UUID. Only the reference inside OnRamp goes; the target of the link itself is not touched.

When to use it
retire a shared folder link once the folder is archived elsewhere.
Watch out
a permanent delete, so double-check the mapping.
40

Delete Tag

Action

In Zapier“Deletes a tag. This action is irreversible.”

Deletes a tag permanently, from the tag ID. Unlike Remove Tag From Project, it erases the tag everywhere, not on one item.

When to use it
clean up campaign tags once the campaign closes.
Watch out
irreversible, and every item carrying it loses the label.
41

Delete Task

Action

In Zapier“Deletes a task. This action is irreversible.”

Removes a task outright, given the task ID. One wrong ID removes the wrong task, so map it from a reliable step.

When to use it
drop tasks for a service the customer cancelled in billing.
Watch out
OnRamp states it is irreversible; Reset Task or Uncomplete Task may be enough.
42

Archive Customer

Action

In Zapier“Marks a specific customer as archived.”

Archives a customer account, given the customer ID. Unlike a delete, it can be undone at any time.

When to use it
a customer churns in your billing tool and the account should leave active lists.
Watch out
Unarchive Customer reverses it, so this is safer than any delete.
43

Archive Data Field

Action

In Zapier“Marks a specific data field as archived.”

Archives a custom data field, from the field UUID.

When to use it
clean up fields after a process change without deleting them.
Watch out
Update Data Field can also switch the archived state, so pick one way and stick to it.
44

Archive Library Module

Action

In Zapier“Archives a library module.”

Archives a reusable module from the library, given the module UUID. It takes the module out of the reusable stock without deleting it.

When to use it
retire an outdated phase so nobody pulls it into new playbooks.
Watch out
it stays recoverable with Unarchive Library Module.
45

Archive Library Task

Action

In Zapier“Archives a library task.”

Archives a single reusable task in the library, from the task UUID.

When to use it
a compliance step is no longer required and should drop out of the library.
Watch out
archiving is reversible; Delete Library Module Task is not.
46

Archive Playbook

Action

In Zapier“Marks a specific playbook as archived.”

Retires a playbook by archiving it, from the playbook UUID.

When to use it
an offer is discontinued and its template should no longer be picked for new projects.
Watch out
Find Playbooks can list archived ones too, so retrieval stays possible.
47

Archive Project

Action

In Zapier“Marks a specific project as archived.”

Archives a project, from its ID. Unlike a delete, it can be undone.

When to use it
clear finished projects from everyone's view when your contract tool marks the customer as renewed or lost.
Watch out
it fires Project Archived; Unarchive Project is the way back.
48

Complete Project

Action

In Zapier“Marks a specific project as complete.”

Marks a project as complete, from its ID.

When to use it
close the project automatically when the final invoice is paid in your accounting tool.
Watch out
this fires the Project Completed trigger, so any Zap listening to it runs too.
49

Mark a Task as Complete

Action

In Zapier“Marks a specific task as complete.”

Ticks off a task, from its task ID.

When to use it
a document gets signed in your e-signature tool and the matching OnRamp task should close itself.
Watch out
unlike most actions here, this task ID is not documented as accepting a UUID; test with the format your source provides.
50

Create a User

Action

In Zapier“Create a new OnRamp User.”

Invites a new person into OnRamp. First name, last name, email address and user role are all required.

When to use it
onboard a new hire automatically when HR adds them to the staff directory.
Watch out
the role must already exist; run Get User Roles to see the valid values first.
51

Move Task

Action

In Zapier“Moves a task to a new position within a module, reordering it within the same project.”

Changes where a task sits within a module, reordering it inside the same project. It requires the task ID.

When to use it
push an urgent task to the top of its module when a priority flag is raised elsewhere.
Watch out
it reorders within the project only; it cannot move a task to another project.
52

Publish Playbook

Action

In Zapier“Publishes a specific playbook.”

Publishes a playbook so teams can start projects from it, given the playbook UUID.

When to use it
release a template automatically once its last module has been approved.
Watch out
publish only after the modules and tasks are in place.
53

Resend User Invite

Action

In Zapier“Resends a specific user's invite email.”

Sends a user's invitation email again, from the user ID.

When to use it
nudge a customer contact who has not logged in when a reminder tool says the kickoff is close.
Watch out
every resend is a task and an email; avoid running it from a trigger that fires often.
54

Reset Task

Action

In Zapier“Resets a specific task to its initial state.”

Puts a task back to its initial state, from the task ID. That goes further than uncompleting it.

When to use it
restart a recurring check, such as a monthly data review, without creating a fresh task.
Watch out
whatever progress the task held is cleared, so use it on purpose.
55

Save Module to Library

Action

In Zapier“Saves a module to the library.”

Copies a project module into the library so it can be reused, from the module ID.

When to use it
a project lead perfects a phase on a live project and wants it saved for the next ones.
Watch out
it wants the ID of a project module, which Module Created or Find Module by ID gives you.
56

Unarchive Customer

Action

In Zapier“Marks a specific customer as not archived.”

Restores an archived customer account to active, from its ID.

When to use it
win-back campaigns: a former customer signs again and you would rather reuse their account than create a new one.
Watch out
if you only have the name, Find Customer gives you the ID first.
57

Unarchive Data Field

Action

In Zapier“Marks a specific data field as unarchived.”

Reactivates an archived data field, using its UUID. It is the reverse of Archive Data Field, and the archived switch of Update Data Field does the same job.

When to use it
a field you retired is needed again for a new reporting request.
Watch out
Find Data Field by UUID confirms its state before you act.
58

Unarchive Library Module

Action

In Zapier“Unarchives a library module.”

Restores a library module from the archive, with its UUID.

When to use it
a process you dropped returns and its module is still the right base.
Watch out
Find Library Modules with the archived switch helps you locate it.
59

Unarchive Library Task

Action

In Zapier“Unarchives a library task.”

Puts an archived library task back in circulation, given its UUID. The task becomes available again for modules and playbooks that need it.

When to use it
a regulation comes back into force and the old task applies again.
Watch out
the UUID also accepts a plain number, as with most library operations.
60

Unarchive Playbook

Action

In Zapier“Marks a specific playbook as unarchived.”

Returns an archived playbook to use, from its UUID. Teams can then reuse the template without rebuilding a single module.

When to use it
a seasonal offer comes back and its template is needed again.
Watch out
check whether it also needs Publish Playbook before teams can pick it.
61

Unarchive Project

Action

In Zapier“Marks a specific project as not archived.”

Brings an archived project back, using the project ID. It is the exact reverse of Archive Project.

When to use it
a returning customer should resume in the same project instead of a new one.
Watch out
any Zap built on Project Unarchived runs as a result.
62

Uncomplete Project

Action

In Zapier“Marks a specific project as not complete.”

Reopens a completed project by marking it not complete, using the project ID.

When to use it
a customer raises a new request after closure and the work must continue in the same project.
Watch out
completing it again later restarts every Zap built on Project Completed.
63

Uncomplete Task

Action

In Zapier“Marks a specific task as not complete.”

Flips a completed task back to open, from the task ID.

When to use it
a deliverable is rejected during review and the task should reappear on the customer's list.
Watch out
the Task Completed trigger will fire again when it is finished a second time.
64

Update Comment

Action

In Zapier“Updates an existing comment.”

Rewrites an existing comment, from its comment UUID and the new message.

When to use it
correct an automated status comment once the real figure arrives from another tool.
Watch out
integer comment IDs are deprecated here; use the UUID.
65

Update Customer by ID

Action

In Zapier“Updates a Customer by ID.”

Changes a customer account's details, with the customer ID as the only required field.

When to use it
keep the customer's address or email current when the CRM record changes.
Watch out
map only the fields you mean to change and test with a real account first.
67

Update Customer Resource

Action

In Zapier“Updates an existing customer resource.”

Edits a resource on a customer account, from the customer ID and the resource UUID.

When to use it
swap a link for a newer version of the contract or the guide.
Watch out
Find Customer Resources supplies the resource UUID.
68

Update Data Field

Action

In Zapier“Updates a data field in the system.”

Changes a data field's settings, from its UUID: required, applied on creation, or archived. One step can tighten a field for every record it covers, without opening OnRamp settings.

When to use it
make a field mandatory on every account once a new policy starts.
Watch out
the archived switch duplicates Archive Data Field.
69

Update Data Field Option

Action

In Zapier“Updates an option on a dropdown or multi_select data field.”

Edits an option of a dropdown or multi_select field, given the field UUID and the option ID.

When to use it
correct a misspelled choice in sync with your CRM picklist.
Watch out
Find Data Field Options returns the option IDs.
70

Update Data Field Value

Action

In Zapier“Updates a data field value in the system.”

Sets one stored value of a data field, from the value UUID and the new value. It can create a missing dropdown option on the fly.

When to use it
write a customer's plan into OnRamp after an upgrade.
Watch out
leave the create-option switch off if you want typos rejected.
71

Update Library Module

Action

In Zapier“Updates a library module.”

Edits a reusable module in the library, from its UUID. Only the module UUID is required, and it usually comes from Find Library Modules, so the step stays short to set up.

When to use it
rename a standard phase across your library.
Watch out
the UUID field also takes a plain number.
72

Update Library Module Task

Action

In Zapier“Updates a task within a library module.”

Changes a task within a library module, with the module UUID and the task UUID. This keeps the reusable phase accurate without rebuilding it from scratch.

When to use it
update an instruction inside a standard phase.
Watch out
both identifiers are required; a single missing one stops the step.
73

Update Library Task

Action

In Zapier“Updates a library task.”

Edits a standalone library task, from its UUID. Fixing the library copy once spares you the same correction in every future playbook.

When to use it
keep a reusable compliance step aligned with the latest policy text.
Watch out
Find Library Tasks gives you the UUID.
74

Update Module by ID

Action

In Zapier“Updates a specific Module.”

Edits a specific project module, found by its module ID.

When to use it
rename a phase across a project when a contract amendment changes its scope.
Watch out
this edit will fire Module Updated in any Zap listening for it.
75

Update Playbook

Action

In Zapier“Updates a playbook in the system.”

Edits a playbook, from its UUID, including whether it is archived. The playbook UUID is required, and the field accepts a plain number as well.

When to use it
rename a template when the offer it serves changes name.
Watch out
the archived switch overlaps with Archive Playbook.
76

Update Playbook Module

Action

In Zapier“Updates a module within a playbook.”

Changes a module inside a playbook, with the playbook UUID and the module UUID. Both identifiers are required, each one accepting a number or a UUID.

When to use it
adjust a template phase after a retrospective.
Watch out
Find Playbook Modules returns the UUIDs for that playbook.
77

Update Playbook Task

Action

In Zapier“Updates a task within a playbook.”

Edits a task within a playbook, given the playbook UUID and task UUID. It changes the template, not a running project.

When to use it
reword a template step from an approved change request.
Watch out
Find Playbook Tasks gives you the task UUID.
79

Update Project Note

Action

In Zapier“Updates an existing project note.”

Changes an existing project note, given its note UUID.

When to use it
refresh a status note each time a report is generated in your BI tool.
Watch out
it fires Project Note Updated, so keep the two in different Zaps.
80

Update Project Resource

Action

In Zapier“Updates an existing project resource.”

Updates a resource attached to a project, with the project ID and the resource UUID.

When to use it
point a project at the latest training deck when your library tool publishes it.
Watch out
without the resource UUID the step fails; fetch it with Find Project Resources.
81

Update Subtask / Set Answer

Action

In Zapier“Updates a subtask, including setting its answer/response.”

Updates a subtask and can set its answer, from the subtask ID.

When to use it
fill in a questionnaire answer for the customer from the form they already completed elsewhere.
Watch out
never pair it with Subtask Updated in one Zap.
82

Update a Task

Action

In Zapier“Update a specific Task by its ID”

Modifies a task, identified by its task ID. Only the task ID is mandatory, so the step changes just the fields you choose to map.

When to use it
move a due date when a dependency in your engineering tracker slips.
Watch out
started from Task Updated, it rewrites the task and triggers itself again.
83

Update a User by ID

Action

In Zapier“Updates a specific user by ID.”

Edits a user, found by the user ID, including whether the account is active.

When to use it
deactivate a leaver's access when HR closes their file.
Watch out
map the Is Active field only when you really mean to switch someone off.
84

Remove Playbook Module

Action

In Zapier“Removes a module from a playbook. This action is irreversible.”

Removes a module from a playbook, using the playbook UUID and the module UUID.

When to use it
drop a phase from a template once a process step is abolished.
Watch out
OnRamp states this is irreversible; check the module UUID with Find Playbook Modules first.
85

Remove Project Member

Action

In Zapier“Removes a member from an existing project.”

Takes a user off a project, from the project ID and the user ID.

When to use it
an account manager changes portfolio and should leave the old projects.
Watch out
Find Project Members shows who is on it before you remove anyone.
86

Remove Tag From Customer

Action

In Zapier“Removes a tag from a customer.”

Strips a tag from a customer account, using the customer ID and the tag ID. The customer record itself stays untouched apart from that one label.

When to use it
drop an at-risk label once the customer renews.
Watch out
the tag itself survives; only the link is removed.
87

Remove Tag From Module

Action

In Zapier“Removes a tag from a module.”

Detaches a tag from a module, given the module ID and the tag ID. The module keeps its tasks and its other tags, and only this label goes away.

When to use it
clear a blocked flag when a partner delivers.
Watch out
both IDs are required, number or UUID.
88

Remove Tag From Project

Action

In Zapier“Removes a tag from a project.”

Pulls a tag off a project, from the project ID and the tag ID.

When to use it
remove an urgent label once the go-live date passes.
Watch out
may fire Project Updated in other Zaps; test the side effects.
89

Remove Tag From Task

Action

In Zapier“Removes a tag from a task.”

Removes a tag from a task, with the task ID and the tag ID. Everything else about the task stays as it was, including comments and subtasks.

When to use it
lift a waiting-on-customer tag when their reply arrives.
Watch out
Find Tags turns a label name into the tag ID.
90

Remove Tag From User

Action

In Zapier“Removes a tag from a user.”

Untags a user, given the user ID and the tag ID. The label disappears from that person only, while other users keep it.

When to use it
a contact stops being the decision maker according to your CRM.
Watch out
nothing else about the user changes.
91

Update Customer Note

Action

In Zapier“Updates an existing customer note.”

Edits a customer account note, from the customer ID and the note ID.

When to use it
maintain one living summary note per customer instead of piling up new ones.
Watch out
Find Customer Notes lists the note IDs for that customer.
92

Update Project by ID

Action

In Zapier“Updates a Project by ID.”

Edits an existing project, located by its project ID.

When to use it
push a new target date from your CRM into OnRamp when the deal timeline changes.
Watch out
it can fire Project Updated, so never run it from that trigger in the same Zap.
93

Update Tag

Action

In Zapier“Updates an existing tag.”

Renames or adjusts an existing tag, from its tag ID. Only the tag ID is required, which keeps the step short to configure.

When to use it
rename a segment tag when marketing renames the segment.
Watch out
every customer, project or task carrying that tag shows the new version.
Searches

OnRamp searches: find what already exists

46 search steps look for data that already exists in OnRamp, so a later step can use it.

A search step looks up an existing record so later steps can use it. OnRamp's 46 searches sit at the bottom of the Action event list, under SEARCH. Some action fields also offer + Add search step, which inserts one and wires it in. Any search makes the Zap multi-step, so it needs a paid plan.

1

Find Comment

Search

In Zapier“Finds a specific comment by UUID.”

Looks up one comment from its UUID and passes its content to the next steps.

When to use it
a notification carries a comment reference and you need the full text to forward.
Watch out
integer comment IDs are deprecated; only the UUID is reliable.
2

Find Customer

SearchFind or create

In Zapier“Finds a Customer in the system.”

Searches customers by name, the only required field. Its find-or-create twin, Find or Create Customer, is this same search with creation ticked: when no customer matches that name, it creates one.

When to use it
a form sends a company name and the next step needs the customer ID.
Watch out
creation needs the fields Create Customer requires.
3

Find Customer by ID

Search

In Zapier“Finds a Customer by ID or UUID.”

Fetches a customer's full record from its ID or UUID.

When to use it
a trigger gives only the customer ID and an email step needs the address.
Watch out
it needs the ID; with only a name, Find Customer is the right search.
5

Find Customer Notes

Search

In Zapier“Lists all notes for a customer.”

Returns all notes of a customer account, given its ID.

When to use it
gather the account history before a renewal reminder goes out.
Watch out
by default only the first note continues; switch to all results if you need the full set.
6

Find Customer Note by ID

Search

In Zapier“Finds a specific customer note by ID or UUID.”

Retrieves one customer note, needing both the customer ID and the note ID. It returns a single note, so the multiple-results setting rarely matters here.

When to use it
read a note's latest text before overwriting it with Update Customer Note.
Watch out
both IDs accept a number or a UUID.
7

Find Customer Resources

Search

In Zapier“Lists all resources for a customer.”

Lists the resources linked to a customer account, from the customer ID.

When to use it
check whether the contract link is already there before adding it twice.
Watch out
leave the no-result setting on if an empty list is normal.
8

Find Data Fields

Search

In Zapier“Finds data fields in the system.”

Searches the custom data fields defined in OnRamp, with optional switches for archived, required and applied-on-creation fields.

When to use it
list every required field before a Zap creates customers in bulk, so none is left blank.
Watch out
its object type choices are the same ones Create Data Field uses.
9

Find Data Field by UUID

Search

In Zapier“Finds a Data Field by UUID.”

Fetches the definition of one data field from its UUID. What comes back tells you the field type and whether it is required.

When to use it
confirm a field's type before writing a value into it.
Watch out
a plain number works too, despite the name.
10

Find Data Field Options

Search

In Zapier“Finds options for a dropdown or multi_select data field.”

Lists the choices of a dropdown or multi_select field, given its UUID. Each option it returns carries the ID that the update and remove actions ask for.

When to use it
get the option ID before Update Data Field Option edits it.
Watch out
point it only at a dropdown or multi_select field.
11

Find Data Field Values

Search

In Zapier“Finds data field values for a data field.”

Returns the stored values of one data field, from the field UUID. It gives a field-wide view, unlike the single-value lookup next to it.

When to use it
audit what customers answered for a given field across accounts.
Watch out
the value UUIDs it returns feed Bulk Update Data Field Values.
12

Find Data Field Value by UUID

Search

In Zapier“Finds a Data Field Value by UUID.”

Reads one stored value, given its value UUID. It returns one value, the exact record the update actions point at.

When to use it
check a value before deciding whether an update is needed.
Watch out
this is the value's UUID, not the field's.
13

Find Events

Search

In Zapier“Finds events in the system.”

Searches the events OnRamp records in the system; no field is required.

When to use it
pull recent events into a report built by another tool.
Watch out
no input narrows it, so test what a run actually returns before mapping.
14

Find Library Modules

Search

In Zapier“Finds library modules in the system.”

Searches reusable library modules, with an optional switch to include archived ones. It covers the reusable modules of the library, not the modules living inside projects.

When to use it
find the module to copy into a new playbook.
Watch out
without that switch, archived modules may stay hidden.
15

Find Library Module by UUID

Search

In Zapier“Finds a Library Module by UUID.”

Fetches one library module from its UUID. You get one module back, the same one the archive and update actions target. The UUID usually comes from Find Library Modules.

When to use it
read a module's current name before renaming it.
Watch out
the UUID box accepts plain numbers as well.
16

Find Library Tasks

Search

In Zapier“Finds library tasks in the system.”

Searches the library's reusable tasks, optionally among archived ones. It looks only at the library, never at tasks inside running projects.

When to use it
locate a standard step before adding it to a module.
Watch out
several matches mean deciding between first, stop or all.
17

Find Library Task by UUID

Search

In Zapier“Finds a Library Task by UUID.”

Retrieves a single library task, given its UUID. One exact task comes back, ready for the update or archive actions.

When to use it
check a task's wording before Update Library Task changes it.
Watch out
an unknown UUID returns nothing and stops the Zap by default.
18

Find Module

Search

In Zapier“Finds a Module in the system.”

Searches project modules in the system without a required field. Unlike Find Module by ID, it works as a broad search.

When to use it
locate a module when the trigger did not carry its ID.
Watch out
many modules may match, so set the multiple-results rule.
19

Find Module by ID

Search

In Zapier“Finds a Module by ID or UUID.”

Fetches one project module by ID or UUID. It returns a single module, and the field accepts a plain number or a UUID. Map it from Module Created or from a task step to read the module before acting on it.

When to use it
get the module UUID that Create Task needs.
Watch out
a deleted module returns nothing.
20

Find Playbooks

Search

In Zapier“Finds playbooks in the system.”

Lists playbooks, with an optional switch for archived ones. Each playbook it finds carries the UUID that every playbook action asks for.

When to use it
pick the template for a new project when only its name is known.
Watch out
the default keeps only the first match.
21

Find Playbook by UUID

Search

In Zapier“Finds a Playbook by UUID.”

Reads one playbook from its UUID. It returns a single playbook with its details. The UUID usually comes from Find Playbooks, or from a value stored in another tool when you first created the template.

When to use it
read a template's details before a Zap starts projects from it.
Watch out
a plain number also works.
22

Find Playbook Data Fields

Search

In Zapier“Finds the data fields of a playbook.”

Returns the data fields a playbook uses, from its UUID. The result helps you prepare the values a new project from that playbook will expect.

When to use it
know which fields to fill before creating a project from that template.
Watch out
expect several results.
23

Find Playbook Modules

Search

In Zapier“Finds the modules of a playbook.”

Lists the modules inside a playbook, given its UUID. Each module it lists comes with the UUID the playbook module actions require.

When to use it
feed module UUIDs into Add Task to Playbook Module.
Watch out
choose all results if every module matters.
24

Find Playbook Roles

Search

In Zapier“Finds the roles of a playbook.”

Returns the roles defined in a playbook, from the playbook UUID. The result lists what a template expects to be staffed.

When to use it
map task roles correctly when a Zap builds a project from that template.
Watch out
roles here are playbook roles, not user roles.
25

Find Playbook Tasks

Search

In Zapier“Finds the tasks of a playbook.”

Lists the tasks of a playbook, given its UUID. Each task listed carries the UUID that the update and delete actions need. The playbook UUID itself comes from Find Playbooks.

When to use it
find the task UUID before Delete Playbook Task removes it.
Watch out
many tasks will match.
26

Find Projects

Search

In Zapier“Finds projects in the system.”

Searches all projects, no required field. It casts the widest net among project searches, with nothing to fill in. Pair it with the multiple-results setting to control how much flows on.

When to use it
loop through projects for a status report built elsewhere.
Watch out
by default only the first project goes on.
27

Get Project Activity

Search

In Zapier“Finds activity feed entries for a project.”

Reads the activity feed of one project, from its UUID. The feed shows what happened on the project, step by step.

When to use it
attach recent activity to a weekly client digest.
Watch out
this field takes the project UUID, though a number works too.
28

Find Project

Search

In Zapier“Finds a Project in the system.”

Looks a project up in the system, without a required field. Unlike Find Project by ID, it behaves as a broad search.

When to use it
find the project for an email that mentions only the customer.
Watch out
test which match comes first.
29

Find Project by ID

Search

In Zapier“Finds a Project by ID or UUID.”

Fetches a project's full details from its ID or UUID.

When to use it
a task trigger needs the parent project's name for a message.
Watch out
a name will not work here; Find Project or Find Projects handle that case.
31

Find Project Members

Search

In Zapier“Finds the members of a project.”

Returns who is on a project, from its UUID. The members it returns carry the user IDs other actions ask for.

When to use it
notify the whole project team about a milestone.
Watch out
choose all results, or only the first member is used.
32

List Project Notes

Search

In Zapier“Lists all notes for a project.”

Gathers every note of a project, given the project ID. Each note it returns carries the UUID that the update and delete actions expect.

When to use it
compile a handover document at project completion.
Watch out
long lists may be heavy for the next step.
33

Find Project Resources

Search

In Zapier“Lists all resources for a project.”

Lists resources attached to a project, from the project ID. Every resource returned carries the UUID the update and delete actions ask for.

When to use it
get the resource UUID before updating a link.
Watch out
an empty list stops the Zap by default.
34

Find Statuses

Search

In Zapier“Finds statuses in the system.”

Returns the statuses defined in OnRamp. It takes no input at all and returns what the account defines.

When to use it
translate a status into a label your reporting tool understands.
Watch out
no input is required, so expect the full list.
35

Find Subtask

Search

In Zapier“Finds a specific subtask by ID or UUID.”

Fetches a subtask from its ID or UUID. It returns a single subtask, and the ID field accepts a number or a UUID. The ID often comes from List Task Subtasks or from a subtask trigger.

When to use it
read a customer's answer before acting on it.
Watch out
a deleted subtask returns nothing.
36

Find Tags

SearchFind or create

In Zapier“Finds tags by name or color.”

Searches tags by name or colour. Find or Create Tag is the same search with creation switched on: when no tag with that name and colour exists, it makes one.

When to use it
turn a label into the tag ID that Add Tag to Project requires.
Watch out
the colour is part of the match.
37

Find Tag by ID

Search

In Zapier“Finds a Tag by ID or UUID.”

Reads one tag, given its ID or UUID. The tag it returns carries its name, ready for a readable message.

When to use it
show a tag's name in a message when the trigger only carries its ID.
Watch out
deleted tags are gone for good.
38

Find Tasks

Search

In Zapier“Finds tasks in the system.”

Searches tasks, with an optional overdue switch. It searches across tasks broadly, which makes the overdue switch the main way to narrow it.

When to use it
collect overdue tasks for a reminder email built in another app.
Watch out
set the multiple-results rule to all if you want them all.
39

Find Task

Search

In Zapier“Finds a Task in the system.”

Looks a task up in the system, also with the overdue switch.

When to use it
check whether a specific task is late before escalating.
Watch out
without a precise input, the first match may not be the one you mean.
40

List Task Comments

Search

In Zapier“Lists all comments for a task.”

Gathers all comments on a task, from its ID. The comments come back in one result set, ready to be passed on together.

When to use it
attach the discussion to a ticket you escalate.
Watch out
choose all results to keep the whole thread.
41

Find Task by ID

Search

In Zapier“Finds a Task by ID or UUID.”

Fetches a task's details by ID or UUID. It returns one exact task, the counterpart of the broader Find Task.

When to use it
a comment trigger needs the task name for a notification.
Watch out
a removed task returns nothing.
42

List Task Subtasks

Search

In Zapier“Lists all subtasks for a task.”

Lists the subtasks under a task, given the task ID. The subtasks it returns each carry the ID that Update Subtask / Set Answer expects.

When to use it
check every checklist item is done before closing the parent.
Watch out
only the first subtask continues unless you change the setting.
43

Find User

Search

In Zapier“Finds a User in the system.”

Searches users, with an optional switch for customer users. Unlike Find User by ID, it is a broad search.

When to use it
find the staff member who should join a project.
Watch out
leave the customer switch off when you want staff only.
44

Find User by ID

Search

In Zapier“Finds a User by ID or UUID.”

Reads a user's record from the user ID or UUID. It returns exactly one user record.

When to use it
get an email address for a message to the person a trigger names.
Watch out
the field accepts a plain number or a UUID.
45

Get User Roles

Search

In Zapier“Get Available User Roles”

Returns the user roles available in OnRamp. It needs no input and simply returns every role defined in the account.

When to use it
pick a valid role before Create a User runs.
Watch out
roles are set inside OnRamp; Zapier cannot add new ones.
46

Find Webhooks

Search

In Zapier“Finds webhooks in the system.”

Lists the event subscriptions registered on the OnRamp account, the channels the app uses to report events to outside tools.

When to use it
audit what the account sends out when a trigger behaves oddly.
Watch out
it reads only; nothing can be changed from this search.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there. Switch it on and the Zap carries on without the result.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: it asks for the fields needed to create the missing item, and the setting above disappears.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or hand every match on at once.
When it breaks

When an OnRamp Zap breaks

Zapier ties no help article to OnRamp, so the cases below are Zapier's general limits plus what OnRamp's own operations state.

Most broken OnRamp Zaps come from a loop, a missing ID or a delete nobody can undo. If a Zap misbehaves anyway, Zapier troubleshooting covers the general method, and the Zapier review sums up the tool.

  • The past is not picked up

    A Zap only reacts to what happens after you switch it on. Projects and tasks that already existed stay untouched; moving that backlog is a separate job.

  • A Zap that triggers itself

    Writing into the very place your trigger watches, such as Add Comment to Task on a Comment Created Zap, sets it off again and again and burns tasks fast.

  • A sudden flood of events

    A bulk import or a migration that creates many tasks at once can return a huge batch, and Zapier's flood protection may hold it back.

  • Deletes cannot be undone

    OnRamp marks nearly all of its delete actions as irreversible. A wrong mapping on Delete Task or Delete Module erases real work, so test on dummy records.

  • Integer comment IDs

    Comment operations now want the comment UUID; integer comment IDs are deprecated, so an old mapping may stop finding anything.

  • A search that finds nothing

    By default, a search with no result stops the Zap and skips the steps that depended on it. Turn on the no-result setting when empty is normal.
Need help

Need help automating OnRamp with Zapier?

A person reads every message.

FAQ

OnRamp Zapier integration: frequent questions

01Is the OnRamp Zapier integration free?
Yes, OnRamp is not reserved to paid plans, so it works on Zapier's free plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. Add a second action, a filter or a search step, the Zap becomes multi-step and needs a paid plan. Plenty of useful OnRamp Zaps fit in two steps, like Project Completed followed by Archive Project, so the free plan is a fair place to test before deciding.
02How many tasks does an OnRamp Zap use?
One task per action that succeeds, nothing for the trigger. If Task Completed starts a Zap that runs Add Comment to Task, each completed task costs one task on your plan. A Zap with three actions spends three per run. An action that fails is not counted. Watch the loops: a Zap that writes where its own trigger listens restarts itself and can empty a monthly allowance quickly. Also count how busy the trigger is, since Task Updated fires far more often than Project Completed.
03Is OnRamp to Zapier real time?
Yes. All 28 OnRamp triggers are instant: OnRamp reports each event to Zapier itself, so the Zap starts right away whatever your plan. The polling interval grid, where the free plan waits for checks, does not apply to any of them. In the editor, a lightning bolt on the trigger confirms it. The only delay you may meet is Zapier holding back an unusually large batch of events, for instance after a bulk import or a migration.
04What does it take to connect OnRamp to Zapier?
An OnRamp account and access to whatever the Zap should touch. In Zapier, open Apps, click + Add connection, search OnRamp, click Add connection, then sign in to OnRamp in the tab that opens and grant access. The connection is saved once and reused by every OnRamp step. If the Zap must act on projects or customers you do not own, your account needs read or write access to them, or the actions will fail.
05Why does an OnRamp action keep asking for an ID?
Because most OnRamp actions locate their target by ID: a project ID, a customer ID, a task ID or a tag ID. Most of these accept either a plain number or a UUID. When the trigger already carries the ID, map it directly. When you only know a name, put a search in front, such as Find Customer or Find Tags, and map the ID it returns. That extra search makes the Zap multi-step, so it needs a paid plan.
06What if the OnRamp operation you need doesn't exist?
Check the three lists first: with 28 triggers, 93 actions and 46 searches, most onboarding events and edits are covered, often under a name you did not expect, like Update Subtask / Set Answer. If the event truly is missing, a nearby trigger plus a filter can narrow it down, on a paid plan. If the action is missing, a search followed by an update sometimes gets you there. Otherwise, the operation simply is not offered by OnRamp on Zapier today.
07Zapier, Make or n8n for OnRamp?
It depends on what you value. On Zapier, OnRamp brings 28 instant triggers, 93 actions and 46 searches, it works on the free plan, and every Zap starts the moment the event happens. The free plan limits you to two-step Zaps and 100 tasks a month, so complex onboarding flows with searches and filters mean a paid plan. Hold those criteria against the OnRamp coverage of each other tool before choosing, and read the comparisons on this site for the wider picture.
Same platform

Other docs you might need on this stack.

Browse all integrations