Connect Hjarni and Reply

Both apps 38Hjarni 15Reply 23

• Trigger
  New Note

  Triggers when a new note is created.

• Action
  Add File to Note

  Attaches a file to an existing note from a URL.

• Action
  Add tag

  Create a tag.

• Action
  Create Folder

  Creates a new folder with a name, parent folder, description, and AI instructions.

• Action
  Create Note

  Creates a new note with a title, body, tags, and folder.

• Action
  Delete folder

  Delete a container.

• Action
  Delete note

  Delete a note (moves to trash).

• Action
  Delete tag

  Delete a tag.

• Action
  Get folder

  Fetch one container by id.

• Action
  Get note

  Fetch one note by id with body, tags, container, files.

• Action
  List notes

  List notes, filter by scope/container_id/tag, paginated.

• Action
  List tags

  List tags.

• Action
  Update folder

  Update a container.

• Action
  Update note

  Update note fields (title, body, tags, container, append_body etc, expected_lock_version).

• Action
  Update tag

  Rename/update a tag.

• Trigger
  Inbox Category Set for Reply

  Triggers when an email reply in Reply is given an inbox category, automatically or by a user.

• Trigger
  New Email Opened

  Triggers when a contact opens a tracked email sent from Reply.

• Trigger
  New Emails Sent

  Triggers when Reply sends an email from a sequence step.

• Trigger
  New Link Clicked

  Triggers when a recipient clicks a tracked link in an email sent from Reply.

• Trigger
  New Person Bounce

  Triggers when an email sent from Reply bounces or is rejected by the recipient's mail server.

• Trigger
  New Person Opt Out

  Triggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact).

• Trigger
  Prospect Finished

  Triggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually.

• Action
  Add contact list

  Creates a new contact list in Reply, optionally shared with your team.

• Action
  Add note to contact

  Adds a note to a contact's timeline in Reply.

• Action
  Add sequence

  Creates a new sequence in Reply with its steps, schedule, sending accounts and settings.

• Action
  Create\Update Person

  Creates a Reply contact, or updates the existing contact with the same email address.

• Action
  Delete contact

  Deletes a contact from your Reply account.

• Action
  Find contacts by criteria

  Returns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step.

• Action
  Get contact

  Returns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields.

• Action
  Get sequence

  Returns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps.

• Action
  List contact lists

  Returns the contact lists you own plus those shared with your team, optionally filtered by name.

• Action
  List contacts

  Returns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL.

• Action
  List inbox categories

  Returns the inbox categories you can file conversations under.

• Action
  List Sequence Contacts

  Returns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status.

• Action
  List sequences

  Returns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name.

• Action
  Mark as Finished

  Marks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps.

• Action
  Remove Person From Campaign

  Removes a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account.

• Action
  Send Test Webhook Event

  Sends a test event from an existing Reply webhook subscription to its configured URL.

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