Connect Heartbeat to Ontraport

Both apps 29Heartbeat 10Ontraport 19

• Trigger
  Abandoned Invitation Link

  Triggers when someone enters their information in an invitation link, but does not make a purchase or create their account. This will trigger after 4 hours, if the user still has not made a purchase or created their account.

• Trigger
  Course Completed

  Triggers when a user completes a course.

• Trigger
  New Event

  Triggers when a new event is created.

• Trigger
  New Event RSVP

  Triggers when someone RSVPs to an event.

• Action
  Create Event

  Creates an event in a Heartbeat community and optionally invites people or groups.

• Action
  Create Group

  Creates a group in a Heartbeat community, optionally nested under another group and seeded with members.

• Action
  Create Thread

  Posts a new thread in a Heartbeat channel.

• Action
  Deactivate User

  Removes a person's access to a Heartbeat community by email. Their threads, comments and messages stay in place.

• Action
  List Channels

  Returns all channels in the Heartbeat community, with each channel's name, emoji and type.

• Action
  List Threads

  Returns all threads posted in a Heartbeat channel, with each thread's body, author, link and creation time.

• Trigger
  New Contact

  Polling trigger: fires for each newly created contact, newest first (sorted by creation date).

• Trigger
  New or Updated Contact

  Polling trigger: fires when a contact is created or modified, sorted by date last modified.

• Trigger
  New Task

  Polling trigger: fires for each newly created task (objectID 1), newest first.

• Trigger
  New Transaction

  Polling trigger: fires for each newly created transaction (objectID 46), newest first.

• Trigger
  Two-way sync new or updated contact

  A trigger for two-way syncing new and updated contacts, with enhanced on-the-fly mapping. Polls Ontraport Contacts sorted by date-last-modified descending; fires for each new or updated contact.

• Action
  Create Object

  Create a record of any Ontraport object type. Provide objectID and a JSON of fields. Note: Ontraport DROP (dropdown) custom fields fail OPEN — sending a value that is not one of the field's defined options returns HTTP 200 and silently discards it, leaving the field unset. Verify a dropdown value landed by reading the record back.

• Action
  Create or Update Contact

  Create a new contact, or merge into an existing one matched by email (Ontraport saveorupdate). Note: Ontraport DROP (dropdown) custom fields fail OPEN — sending a value that is not one of the field's defined options returns HTTP 200 and silently discards it, leaving the prior value in place. Verify a dropdown value landed by reading the record back.

• Action
  Create Task

  Create a Task object (objectID 1) in Ontraport.

• Action
  Delete Contact

  Delete a contact by its Ontraport ID.

• Action
  Delete Object

  Delete a record of any object type by objectID and id.

• Action
  Find Contact by Email

  Find a contact by exact email match. Returns the first matching record.

• Action
  Find contact by field (Go only has Find Contact by Email — covers email lookup only, not arbitrary field)

  Returns the details for a contact if the specified field matches the specified value. Throws an error if zero or multiple match.

• Action
  Get Contact

  Retrieve a single contact by its Ontraport ID.

• Action
  Get Object

  Retrieve a single record of any object type by objectID and id.

• Action
  List Contacts

  List contacts with optional search, range, and sort.

• Action
  List Objects

  List records of any object type with optional search and range.

• Action
  Remove Tag from Contact

  Remove a tag from one or more contacts.

• Action
  Tag Contact

  Add a tag to one or more contacts.

• Action
  Update Object

  Update a record of any Ontraport object type by ID. Note: Ontraport DROP (dropdown) custom fields fail OPEN — sending a value that is not one of the field's defined options returns HTTP 200 and silently discards it, leaving the prior value in place. Verify a dropdown value landed by reading the record back.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.