Moxo + Webhooks by Zapier

Moxo + Webhooks by Zapier integrations

Manage Moxo flow updates by triggering get actions in Webhooks by Zapier

This workflow streamlines your process by reacting to changes in Moxo app. Whenever there's a Flow Update in Moxo, it triggers a GET operation in Webhooks by Zapier, establishing a seamless connection between these two applications. It eliminates manual data transfer, saving you time and making your operations more efficient. Make real-time responses to updates in Moxo and enhance your work productivity with this workflow.

When this happens...
Flow UpdatesTriggers when a flow or any of its steps is started, completed, or due_date_arrive.
TriggerInstant
automatically do this!
GETFire off a single GET request with optional querystrings.
ActionWrite

Start free with email

Start free with Google

Free forever for core features
14 day trial for premium features & apps

More things you can do with Moxo and Webhooks by Zapier

Discover other triggers and actions you can use with Moxo and Webhooks by Zapier

- Id_explain
- Zap Unique ID Label
- Flow Template Folder
- Moxo Flow Template
  Required
Trigger
Instant
Try It
- Trigger Identifier
Trigger
Instant
Try It
- Specify the way to locate Flow Workspace
  Required
- Binder Reference/Flow Workspace ID
  Required
- Specify the step type
  Required
- Moxo Content-Library Folder
- Moxo Content-Library
  Required
- Step Title
- Step Reference ID
- Is it to add step to the end of flow?
- Step Order Number in the Flow if not to the end of flow
- Step Description
- Due in Days
- Skipped Weekends for Due in Days
- Allow parallel processing for multiple assignees, whose order is upon the sequence in the array of Assignee Email
- When allow parallel processing for multiple assignees, the completion type to complete the process. By default, it is All Assignees
Action
Write
- Invite_explain
- Workspace ID
  Required
- Member Email
  Required
- Create New Relationship?
  Required
Action
Write
- Client First Name
  Required
- Client Last Name
  Required
- Client Email
  Required
- Display User ID
- Display User Phone Number
- Rm_explain
- Account Managers
  Required
Action
Write

- Workspace ID
  Required
- Note Name
  Required
- Note Content
  Required
- Editable by
  Required
Action
Write
- Title
  Required
- Sub-Title
  Required
- Content
  Required
- Assigned Client
  Required
- Approval Button Label
- Decline Button Label
- Trigger Identifier for Transaction Completed Event
- Attachments
Action
Write

- Client Email (Identifier)
  Required
- Client First Name
  Required
- Client Last Name
- Display User ID
- Display User Phone Number
- Rm_explain
- Account Managers
  Required
Action
Write
- Workspace ID
  Required
- Specify the object type
- Moxo Content-Library Folder
- Moxo Content-Library
- Description
- Callback URL
- Payload for Confirm Button
- Payload for Other Button
- Due in Days
- Skipped Weekends for Due in Days
- Allow parallel processing for multiple assignees, whose order is upon the sequence in the array of Assignee Email
- When allow parallel processing for multiple assignees, the completion type to complete the process. By default, it is All Assignees
Action
Write
- Purchase Order ID
  Required
Action
Write
- Invite_explain
- Meeting ID
  Required
- Participant Email
- Participant Unique ID
Action
Write
- Workspace ID
  Required
- Folder Name
- File
  Required
Action
Write
- Destination Workspace ID
  Required
- E-Sign Title
- E-Sign Description
- Due in Days
Action
Write
- Flow Name
  Required
- Welcome Message
- Description
- Reference ID
- Member Email
Action
Write
- Workspace ID
  Required
Action
Search
- Intg_explain
- Reference ID
  Required
Action
Search
- Pick off a Child Key
Trigger
Instant
Try It
- Method
  Required
- URL
  Required
- Data Pass-Through?
- Data
- Unflatten
- Basic Auth
- Headers
- Return Raw Response
Action
Write
- URL
  Required
- Payload_type
- Data
- Wrap Request In Array
- File
- Unflatten
- Basic Auth
- Headers
Action
Write

- Id_explain
- Zap Unique ID Label
- Reference ID
- Pre-configured Payload Info
Trigger
Instant
Try It
Xero Purchase Order Completed
Trigger when a Xero Purchase Order is approved or declined in Moxo.
Trigger
Instant
Try It
- Specify the way to locate Flow Workspace
  Required
- Specify the step type
- Step Reference ID
- Is it to add step to the end of flow?
- Step Description
- Due in Days
- Allow parallel processing for multiple assignees, whose order is upon the sequence in the array of Assignee Email
- When allow parallel processing for multiple assignees, the completion type to complete the process. By default, it is All Assignees
Action
Write
- Step Reference ID
  Required
Action
Write
- Workspace Title
  Required
- Welcome Message
- Workspace Owner (Account Manager)
  Required
- Workspace Members
  Required
Action
Write
- Workspace ID
  Required
- Whether to use Content Library Template?
- Description
- Mark As Important?
- Set A Due Date
- Assign To
Action
Write
- Workspace ID
  Required
- Specify the object type
- Transobject Title
- Description
- Callback URL
- Payload for Confirm Button
- Payload for Other Button
- Due in Days
- Skipped Weekends for Due in Days
- Assignee Email
  Required
- Allow parallel processing for multiple assignees, whose order is upon the sequence in the array of Assignee Email
- When allow parallel processing for multiple assignees, the completion type to complete the process. By default, it is All Assignees
Action
Write
- Assigned Client
  Required
- Purchase Order ID
  Required
- Purchase Order Number
  Required
- Purchase Order Title in Moxo
  Required
- Purchase Order Sub-Title in Moxo
  Required
- Approval Button - Label
- Decline Button - Label
- Address
- Period
- UTR
Action
Write
- Client Email (Identifier)
  Required
Action
Write
- File (Download) URL
  Required
Action
Write
- Topic
  Required
- Agenda
- Start Time
  Required
- End Time
- Time Zone
  Required
- Meeting Host User Entity Type
- Meeting Participants (Email)
- Meeting Participants (Unique ID)
- Meeting Binder
- Max Minutes Attendee Can Join Before Host
Action
Write
- Workspace ID
  Required
- Message
  Required
Action
Write
- Flow Template Folder
  Required
- Moxo Flow Template
  Required
- Role_user_explain
- Flow Name
  Required
- Workspace Owner
- Welcome Message
- Description
- Reference ID
Action
Write
- Client Email (Identifier)
  Required
- Client First Name
- Client Last Name
- Display User ID
- Display User Phone Number
- Rm_explain
- Account Managers
Action
Write
- Conv_explain
- Client's Email
  Required
- Account Manager's Email
  Required
Action
Search
Catch Raw Hook
Triggers when a POST, PUT, or GET request is made to a Zapier URL. Gives the request body unparsed (max 2 MB) and also includes headers.
Trigger
Instant
Try It
- URL
  Required
- Key
- Deduplication Key
- Xpath
- Basic Auth
- Headers
Trigger
Polling
Try It
- URL
  Required
- Query String Params
- Send As JSON
- JSON key
- Unflatten
- Basic Auth
- Headers
Action
Write
- URL
  Required
- Payload_type
- Data
- Wrap Request In Array
- File
- Unflatten
- Basic Auth
- Headers
Action
Write

About Moxo

Moxo is a OneStop Client Interaction Hub.

HelpHelp

Related categories

Team Collaboration

About Webhooks by Zapier

Webhooks simply POST data (or JSON) to a specific URL every time we see something new. Webhooks can also accept data (or JSON) to kick off a workflow in Zapier.

Learn moreLearn moreHelpHelp

Related categories

Developer Tools

Premium

Zapier