HubSpot Custom Field API Names for Workflow Triggers

Last updated: April 20, 2026

This article applies only if you want to trigger OnRamp workflows using a custom HubSpot field. If you're using other trigger methods (such as deal stage changes or standard HubSpot properties), these requirements do not apply.

When configuring HubSpot workflows to trigger project creation in OnRamp via a custom field, that field must follow a specific API naming convention. This ensures our integration can correctly detect and act on your workflow conditions.

Required API Names

OnRamp listens for up to five custom trigger fields on HubSpot objects. These fields must use the exact API names below:

  • onramp_condition_1

  • onramp_condition_2

  • onramp_condition_3

  • onramp_condition_4

  • onramp_condition_5

Only fields with these API names will be recognized as valid trigger conditions.

Recommended Primary Trigger Field

For most use cases, we recommend setting up a single primary trigger field:

  • Label: Send to OnRamp

  • Field Type: Checkbox

  • API Name: onramp_condition_1

This field can be used in your HubSpot workflow to indicate when a record is ready to be sent to OnRamp.

Using an Existing HubSpot Field as Your Trigger

If your team already relies on an existing HubSpot field and you'd like that field to drive project creation in OnRamp, do not rename or repurpose the existing field. HubSpot API names cannot be changed after creation, and modifying a field that's already in use can disrupt workflows, reports, and team processes.

Instead, we recommend the following mirror pattern:

  1. Create a new custom field in HubSpot using one of the required API names (e.g., onramp_condition_1).

  2. Limit the field's visibility so it's only accessible to the integration. This keeps your HubSpot UI clean and prevents confusion for users who shouldn't interact with it directly. In the field settings, restrict it from appearing on record views, forms, and other surfaces where your team works.

  3. Create a HubSpot workflow that mirrors the existing field's value into the new onramp_condition_* field. Whenever the existing field is updated, the workflow copies its value to the new field, which then triggers the OnRamp integration.

This way, your team continues using the field they're already familiar with, and the OnRamp integration gets the properly named field it needs — without any changes to existing processes.

Important Notes

  • API names are permanent in HubSpot and cannot be edited after creation — double-check before saving

  • These naming requirements apply only to custom trigger fields — other workflow properties can follow standard HubSpot naming conventions

  • After creating new fields, you must refresh your HubSpot connection in OnRamp for them to appear

Setup Process

  1. Create the custom field in HubSpot

    • Use API name onramp_condition_1 (or another from the approved list)

    • If mirroring an existing field, limit visibility to the integration only and set up a HubSpot workflow to sync values

  2. Configure your HubSpot workflow

    • Set the field value (e.g., check the box) when your trigger criteria are met

  3. Refresh your integration in OnRamp

    • Navigate to Settings → Integrations Plus

    • Refresh your HubSpot connection

  4. Use the field in OnRamp workflows

    • The field will now be available as a trigger condition