Connect Pushbullet to NetHunt CRM

Both apps 38Pushbullet 22NetHunt CRM 16

• Trigger
  New Push

  Polling trigger: fires for each new push received, ordered by modified time.

• Action
  Create Device

  Create a new device on your Pushbullet account.

• Action
  Create Push

  send a push (note, link, or file)

• Action
  Create Subscription

  Subscribe to a channel by its channel tag.

• Action
  Delete All Pushes

  delete all pushes

• Action
  Delete Chat

  Delete a chat by iden.

• Action
  Delete Device

  Delete a device by iden.

• Action
  Delete Push

  Delete a push by iden.

• Action
  Delete Subscription

  Unsubscribe from a channel by subscription iden.

• Action
  Get Channel Info

  Get information about a channel by its tag.

• Action
  Get Current User

  Get information about the authenticated Pushbullet user.

• Action
  List Chats

  List the chats (people you've pushed to) on your account.

• Action
  List Devices

  List the devices on your Pushbullet account.

• Action
  List Pushes

  List pushes, optionally only active and modified after a timestamp.

• Action
  List Subscriptions

  List the channels you are subscribed to.

• Action
  Request File Upload

  request authorization to upload a file

• Action
  Send a Link

  Push a link (title + body + url) to a device, email, channel, or all your devices.

• Action
  Send a Note

  Push a note (title + body) to a device, email, channel, or all your devices.

• Action
  Update Chat

  update a chat (mute)

• Action
  Update Device

  update a device

• Action
  Update Push

  Mark a push as dismissed.

• Action
  Update Subscription

  update a subscription (mute)

• Trigger
  New Call Log

  Triggered when a new call log is added to a record in the specified folder.

• Trigger
  New Comment

  Triggered when a new comment is added to a record in the specified folder.

• Trigger
  New folder

  Triggered when a new folder is added.

• Trigger
  New Google Drive File in Folder

  Polls a NetHunt folder for newly attached Google Drive files linked to its records. Input: folder_id. Returns the list of new Google Drive file attachments.

• Trigger
  New or Updated Record in Folder

  Triggered when a record is created or updated in the specified folder.

• Trigger
  New Record in Folder

  Triggered when a record is created in the specified folder.

• Trigger
  Two-way sync new or updated records in folder

  A trigger for two-way syncing new and updated records in a specified folder, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping.

• Trigger
  Updated Record in Folder

  Triggered when a record is updated in the specified folder.

• Action
  Add Call Log

  Add a call log to the specified record.

• Action
  Add Comment

  Add a comment to the specified record.

• Action
  Delete Record

  Delete a record by ID.

• Action
  Find Record

  Search records in a folder by ID or text query.

• Action
  Find record by field value

  Finds one record in a NetHunt folder by matching a field value, and projects the record's fields map alongside record_id / id / created_at. DYNAMIC OUTPUT — DOCUMENTED EXCEPTION TO THE DESIGN RULE (2026-07-20). The standing rule puts FIND ops in the IDs-only bucket: GET enriches output with a field picker, FIND/LIST return IDs only. This op is a deliberate exception because NetHunt exposes NO get-by-id endpoint, so there is no GET op that could carry the picker. Re-confirmed against live data: ?query=<recordId> returns [] for a record that demonstrably exists in that folder (record 6a48901d931c9b3a9bbfb83c in Contacts), recordId:x 400s, and find-record-by-id 404s. The choice was therefore FIND-or-nothing, and a NetHunt user with no output picker has no way to map folder fields at all. If NetHunt ever ships a get-by-id endpoint, move the picker to a proper GET op and revert this op to IDs-only. Field values are projected under `fields`, a flat object keyed by field NAME, matching the house convention of a dynamic map beside the record's own top-level keys (cf. Agile/Cliniko/Capsule/MINDBODY `custom_fields`). NetHunt has no standard-vs-custom split — every folder field is user-defined — so the whole `fields` object is the dynamic surface and the container keeps the accurate name `fields` rather than `custom_fields`. The picker is parameterized per folder: `folder_id` is a SETTING (not an input) because dynamic-schema resolution binds only against step settings, so an input-sourced folder could never resolve the discovery at automation-load time. TYPE BLINDNESS (inherent, not fixable here): the backing schema endpoint returns only {name} with no type, so the picker advertises every field as String. Live reads return numbers and lists — e.g. Deal amount 100000 and Probability 0.9 are numbers, and Company / Contact person / Manager / Email / Label are ARRAYS (link fields carry record-id arrays). Mapping one of these as a scalar fails at runtime with no design-time signal.

• Action
  List Folder Fields

  List the fields of a folder.

• Action
  List Readable Folders

  List all folders the user can read.

• Action
  List Writable Folders

  List folders the user can create records in.

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