Connect Kit and Sorry

Both apps 31Kit 14Sorry 17

• Trigger
  New Form Subscriber

  Triggers when a subscription occurs on a specific form.

• Trigger
  New Purchase

  Triggers when a new purchase is added to your account.

• Trigger
  New Sequence Subscriber

  Triggers when a subscriber is added to a sequence.

• Trigger
  New Subscriber

  Triggers when a new subscriber is confirmed within your account (has completed any applicable double opt-ins).

• Trigger
  New Unsubscribe

  Triggers when a subscriber unsubscribes from your emails.

• Trigger
  Subscriber Added to Tag

  Triggers when a specific tag is added to a subscriber.

• Trigger
  Tag Removed From Subscriber

  Triggers when a specific tag is removed from a subscriber.

• Action
  Add Subscriber to Form

  Subscribe someone to a specific form.

• Action
  Add Tag to Subscriber

  Add a subscriber to a specific tag.

• Action
  Create or Update Subscriber

  Creates a Kit subscriber, or updates the first name and custom fields of an existing subscriber with the same email address. Returns the subscriber.

• Action
  Find Subscriber

  Finds an existing confirmed subscriber by email.

• Action
  Get Subscriber

  Returns one Kit subscriber by ID, with their name, email address, state and custom field values.

• Action
  List Tags for Subscriber

  Lists the tags on a Kit subscriber, with each tag's ID, name and the date it was applied.

• Action
  Remove Tag From Subscriber

  Remove a specific tag from a subscriber if they have it.

• Trigger
  New notice

  Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.

• Action
  Add component

  Creates a new component on a Sorry status page, optionally nested under a parent component.

• Action
  Add notice

  Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.

• Action
  Add notice update

  Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.

• Action
  Add subscriber

  Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.

• Action
  Delete notice

  Deletes a notice (incident, maintenance or general) from a Sorry status page.

• Action
  Delete subscriber

  Permanently removes a subscriber from a status page.

• Action
  Get notice

  Returns a single notice from a status page, including its type, state, subject, synopsis and link.

• Action
  Get status page

  Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more.

• Action
  List components

  Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.

• Action
  List notices

  Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date.

• Action
  List notice updates

  Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.

• Action
  List status pages

  Returns all status pages in your Sorry account, optionally filtered by name or creation date.

• Action
  List subscribers

  Returns the subscribers on a status page, optionally only those who receive notices for a specific component.

• Action
  Update component

  Updates a component on a Sorry status page, such as its name, description, position or parent component.

• Action
  Update notice

  Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance.

• Action
  Update status page

  Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language.

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