Using HTTP triggers


The HTTP app in Quickwork enables journeys to receive and process data from any external system through webhooks. It acts as a universal connector for applications that do not have native integrations on the platform.

HTTP triggers can:

  • Capture data sent via GET, POST, PUT, or DELETE requests.
  • Initiate journeys automatically when external systems send information.
  • Forward incoming data to other applications for further processing or storage.

Each configured HTTP trigger generates a unique webhook URL that accepts payloads and acknowledges them instantly with a 200 OK response.

Use HTTP triggers when:

  • You want to start a journey whenever an external system sends data.
  • The source application does not have a native connector on Quickwork.
  • You need to capture, process, and forward incoming payloads within Quickwork.