Connect Moxie to DocuPipe

Both apps 61Moxie 45DocuPipe 16

• 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
  Proposal Sent

  [DEPRECATED - Please use "Agreement Sent"] - Triggers when a proposal is sent either via link or email.

• Trigger
  Proposal Signed

  [DEPRECATED - Please use "Agreement Signed"] - Triggers when a proposal is accepted and signed with e-signature.

• Trigger
  Proposal Viewed

  [DEPRECATED - Please use "Agreement Viewed"] - Triggers when a user views the proposal.

• 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
  Document Processed

  Triggers when a document finishes parsing and OCR is complete.

• Action
  Add schema

  Creates a new extraction schema in DocuPipe from a JSON schema you supply, and returns its schema ID.

• Action
  Analyze document

  Asks DocuPipe a list of plain-language questions about one document and starts the analysis, returning the analysis ID to fetch the answers with.

• Action
  Classify Document

  Sends one or more documents to DocuPipe to be sorted into your classes, and returns the job that is doing the work.

• Action
  Delete document

  Removes a document from your DocuPipe account.

• Action
  Delete schema

  Removes an extraction schema from your DocuPipe account.

• Action
  Extract Data From Document

  Pulls structured data out of a document using one of your schemas, and returns the extraction to fetch the results with.

• Action
  Find documents by criteria

  Finds documents in your DocuPipe account whose file name or document ID matches what you search for.

• Action
  Get Document

  Returns one document from your DocuPipe account, with its file details, processing status, parsed text and your own metadata.

• Action
  Get Extraction Result

  Returns the data DocuPipe pulled out of a document, shaped by the schema that was used, along with per-field confidence details.

• Action
  Get schema

  Returns one extraction schema from your DocuPipe account, including the JSON schema it applies and its guidelines.

• Action
  List documents

  Returns the documents in your DocuPipe account, optionally narrowed to one dataset or a date range.

• Action
  List extractions

  Returns the data extractions in your DocuPipe account, optionally narrowed to one schema, one document, or a specific set of extractions.

• Action
  List schemas

  Returns the extraction schemas in your DocuPipe account.

• Action
  Upload and Extract Data

  Sends a file to DocuPipe and immediately starts pulling structured data out of it, returning both the new document and the extraction.

• Action
  Upload Document

  Sends a file to DocuPipe to be read and turned into a document you can extract data from.

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