Cirqll Core
HomeCirqll
HomeCirqll
  1. Zapier
  • Getting Started
  • Translations
  • Documentation
    • Field Values
    • Zapier
      • Triggers
      • Actions
    • Query Parameters
      • Eager Loading
      • Partial Data
      • Count Relations
      • Filter
      • Order By
      • Pagination
    • OAuth2
      • User
      • Client
        • Index
        • Create
        • Update
        • Delete
      • Token
        • Create
        • Refresh
        • Index
      • Scopes
      • Authorize
      • Me
    • Authentication
  • User
    • Me
      GET
    • Index
      GET
    • Show
      GET
    • Create
      POST
    • Update
      PATCH
    • Delete
      DELETE
  • Role
    • Index
      GET
    • Show
      GET
    • Create
      POST
    • Update
      PATCH
    • Delete
      DELETE
  • Customer
    • Index
      GET
    • Show
      GET
    • Delete
      DELETE
    • Update
      PATCH
    • Create
      POST
  • Contact
    • Index
    • Show
    • Create
    • Update
    • Delete
  • Task
    • Index
    • Show
    • Create
    • Update
    • Delete
  • Appointment
    • Index
    • Show
    • Create
    • Update
    • Delete
  • Financial
    • Chance
      • Index
      • Show
      • Create
      • Update
      • Delete
    • Assignment
      • Index
      • Show
      • Create
      • Update
      • Delete
    • Contract
      • Index
      • Show
      • Create
      • Update
      • Delete
  • Email
    • Index
    • Show
    • Create
    • Update
    • Delete
  • Field
    • Index
    • Show
    • Create
    • Update
    • Delete
  • Note
    • Index
    • Show
    • Create
    • Update
    • Delete
  • To-do
    • Index
    • Show
    • Create
    • Update
    • Delete
  • Template
    • Index
    • Show
    • Update
    • Create
    • Delete
  • Setting
    • Index
    • Update
  • Webhook
    • Index
    • Show
    • Create
    • Update
    • Delete
  1. Zapier

Triggers

By using Cirqll's webhook functionality all events are instantly sent to Zapier when they happen. Instantly meaning within around two minutes.
All triggers require only one field: Topics. Below is the New Customer Event as an example:
image.png
The default selection is to only watch for create events. The reason why you can watch for all three events at once is because you can use the Zapier Paths step to handle each seperately in the same Zap, like so:
image.png
If you want to sync items between two platforms based on a certain condition; like a contract price being higher than x, you should watch on both create and update. You must not forget to check if the data already exists in the other platform before duplicating it, of course.
Modified at 2025-10-31 12:28:35
Previous
Zapier
Next
Actions
Built with