Connect Moxie and Sorry

Both apps 59Moxie 42Sorry 17

• Trigger
  Agreement Sent

  Triggers when a proposal is sent either via link or email.

• Trigger
  Agreement Signed

  Triggers when an agreement is accepted and signed with e-signature.

• Trigger
  Agreement Viewed

  Triggers when a user views the proposal.

• Trigger
  Client Created

  Triggers when a new client is created in Moxie.

• Trigger
  Client Deleted

  Triggers when a client record is deleted in Moxie.

• Trigger
  Client Updated

  Triggers when a client record is updated in Moxie.

• Trigger
  Form Completed

  Triggers when a form is completed.

• Trigger
  Invoice Sent

  Triggers when an invoice is sent in Moxie.

• Trigger
  Meeting Cancelled

  Triggers when a meeting is cancelled

• Trigger
  Meeting Scheduled

  Triggers when a new meeting is scheduled

• Trigger
  Meeting Updated

  Triggers when a meeting is updated or rescheduled

• Trigger
  Opportunity Created

  Triggered with a pipeline opportunity is created

• Trigger
  Opportunity Deleted

  Triggered with a pipeline opportunity is deleted

• Trigger
  Opportunity Updated

  Triggered with a pipeline opportunity is updated

• Trigger
  Payment Received

  Triggers when a payment is received either vial Stripe or manual entry.

• Trigger
  Project Completed

  Triggers when a project is set to "complete" in Moxie.

• Trigger
  Project Created

  Triggers when a new project is created in Moxie.

• Trigger
  Project Updated

  Triggers when the settings for a project are updated.

• Trigger
  Task Approval

  Triggers when a new Deliverable is ready for client approval.

• Trigger
  Task Created

  Triggered when a Project Task is created

• Trigger
  Task Deleted

  Triggered when a Project Task is deleted

• Trigger
  Task Updated

  Triggered with a Project Task is updated.

• Trigger
  Ticket Closed

  Triggers and a support ticket is closed

• Trigger
  Ticket Comment

  Triggers when a comment is created on a ticket

• Trigger
  Ticket Created

  Triggers when a new support ticket is created

• Trigger
  Ticket Deleted

  Triggers when a support ticket is deleted

• Trigger
  Ticket Updated

  Triggers when a support ticket is updated

• Trigger
  Time Worked Created

  Triggers when a new time worked entry is created.

• Trigger
  Time Worked Deleted

  Triggers when a time worked record is deleted.

• Trigger
  Time Worked Updated

  Triggers when a time worked entry has been updated.

• Action
  Create Client

  Creates a new client record in Hectic

• Action
  Create Expense

  Records a new expense in your Moxie accounting records, optionally filed under a vendor and allocated to a client.

• Action
  Create Opportunity

  Create a new pipeline opportunity

• Action
  Create & Optionally Send Invoice

  Creates an invoice for a client from the line items you supply, and emails it straight away when you fill in who to send it to. Left blank, the invoice is saved as a draft.

• Action
  Create or Update Calendar Event

  Create or update a calendar event in Moxie

• Action
  Create Project

  Create a project and optionally use a template

• Action
  Create Task

  Create a task in the project management system

• Action
  Create Ticket

  Create a Ticket for a client and contact

• Action
  Create Ticket Comment

  Adds a comment (public or private) to an existing ticket.

• Action
  Create Time Worked

  Creates a time worked entry

• Action
  Delete Calendar Event

  Deletes a calendar event in Moxie by the external ID.

• Action
  Find a Client

  Finds a client by either name or contact email address.

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