Christian Maribong

Make / PROJECT USE CASE

Contract → Invoice → Notification Workflow

End-to-end automation that triggers upon contract signing, creates QuickBooks invoices, sets client variables, and notifies ops team via Slack.

QuickBooksSlackContracts

INTERACTIVE WORKFLOW DEMO

Signed. Invoiced. Team informed.

Sample data · Browser simulation

Inspect the sample client variables, invoice, and operations message created after signing.

Illustrative rules and fictional records. Runs only in your browser; nothing is sent, saved to a server, or connected to the named services. Reloading clears this demo.

  1. 01Contract eventNot run
  2. 02Check signatureNot run
  3. 03Prepare QuickBooks invoiceNot run
  4. 04Preview Slack notificationNot run

1. Set up a scenario

2. Inspect the result

Ready. Run the sample scenario to inspect its outcome.

Change an input and run again to compare the outcome. All previews remain local.

THE BUSINESS NEED

Move from a signed contract to a billing handoff

The challenge

Useful when contract signing needs to initiate invoicing and inform the operations team.

My role

I built a Make workflow connecting contract signing, QuickBooks invoicing, client variables, and Slack notifications.

How the workflow works

  1. Trigger the workflow when a contract is signed.
  2. Create the QuickBooks invoice and set client variables.
  3. Notify the operations team through Slack.

WHAT THE SYSTEM DELIVERS

Contract signing, invoice creation, and the operations notification are connected in one process.

Make · QuickBooks · Slack · Contracts

Contract → Invoice → Notification Workflow workflow overview
Workflow overview · Select the image to inspect it at full size.

HAVE A SIMILAR CHALLENGE?

Let’s connect
the right pieces.

Discuss your automation project ↗
← Explore all automation projects