Connect folk and Reply

Both apps 50folk 27Reply 23

• Trigger
  Company Added

  Triggers when a new company is created or added to a group.

• Trigger
  Company Custom Field Updated

  Triggers when a company custom field (for example tag, status, text, assignee) is updated.

• Trigger
  Company Removed

  Triggers when a company is deleted from the workspace or removed from a group.

• Trigger
  Company Updated

  Triggers when a company basic field (like name, email or URL) in a group is updated.

• Trigger
  Deal Added

  Fires when a new deal is created.

• Trigger
  Deal Removed

  Fires when a deal is deleted from a pipeline.

• Trigger
  Deal Updated

  Fires when a deal is updated (stage change, field update).

• Trigger
  Person Added

  Triggers when a new person is created or added to a group.

• Trigger
  Person Custom Field Updated

  Triggers when a person custom field (for example tag, status, text, assignee) is updated.

• Trigger
  Person Removed

  Triggers when a person is deleted from the workspace or removed from a group.

• Trigger
  Person Updated

  Triggers when a person basic field (like first name, job title, email or URL) in a group is updated.

• Action
  Create Company

  Creates a company in folk, optionally adding it to a group and setting that group's custom fields.

• Action
  Create Deal

  Creates a deal in a folk group, optionally linked to companies and people, and sets that deal type's custom fields.

• Action
  Create Group

  Creates a group in folk. A default "All people" table view is added to the group automatically.

• Action
  Create Note

  Creates a note on a folk person, company or deal. Optionally posts it as a reply to an existing note.

• Action
  Create Person

  Creates a person in folk, optionally adding them to a group and setting that group's custom fields.

• Action
  Create Reminder

  Creates a reminder on a folk person, company or deal, scheduled with an iCalendar recurrence rule.

• Action
  Delete Company

  Deletes a company from folk by its id.

• Action
  Delete Person

  Deletes a person from folk by their id. This also removes their custom fields, notes and associations.

• Action
  Find a Company

  Searches folk companies by name, email or website and returns the matches, with the first one broken out for easy mapping.

• Action
  Find a Person

  Searches folk people by email, full name or phone and returns the matches, with the first one broken out for easy mapping.

• Action
  Get a Company

  Fetches one folk company by id, including its custom field values.

• Action
  Get a Note

  Fetches one folk note by id, with its text, author and the record it is attached to.

• Action
  Get a Person

  Fetches one folk person by id, including their custom field values.

• Action
  List Groups

  Returns the groups in the folk workspace, with each group's id, name and visibility.

• Action
  Update Company

  Updates a folk company. Only the fields you fill in are changed; list fields such as emails replace the whole list.

• Action
  Update Person

  Updates a folk person. Only the fields you fill in are changed; list fields such as emails replace the whole list.

• 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.