What is a Trigger?
Trigger is needed to nudge the recipe to wake up and look for business events to process.
- New contacts added in Google Sheets (327706)
- New tickets in Zendesk
- New Accounts in Salesforce – select action and object (331055)
- Updated incidents in Servicenow
What are different types of triggers?
- Look for new cases created in the last 5 minutes – Poll (331055)
- Salesforce notifying the recipe that an opportunity was updated – Realtime (479643)
- A note about smart Webhooks (uses ping to sweep from last point)
- Query every hour to find cases that match some criteria – Scheduled Search (493363)
- Do something every hour – scheduler (95966) – Advanced option
- Fetch in batches to process in bulk/batch – new batch 4797(57)
- Callable recipes
- Trigger from outside using http – API Gateway
What does a trigger return?
- List of qualifying events are returned
- The list is cached and handed to you one by one – each shows up as an individual job
- Except when it is delivered as batch (479757)
- Delivered in batches specified by the batch size
- Pro – Reduces the number of jobs
- Con – Reduces visibility into individual events being processed
- Each successful job counts as a transaction. Failed jobs don’t count
- Build a recipe to do the right thing – Optimizing for transactions may lead to a poorly built recipe that is inefficient.
How Triggers in Workato simplify the integration challenges:
- Workato maintains pointer/cursor to last record processed
- Smart de-duplication ensures the events are delivered atleast once and only once
- In sequence delivery will present the events in chronological order
- Guaranteed loss-less delivery ensures no events are lost even if apps or recipes are down
How to control what events get processed?
From : Time Machine
- From parameter to pick up events from the past
- Select from drop down list
- By entering custom value
- Once set and run cannot be changed
- Only way out is to make a copy of the recipe and run again
- Can create duplicates – it is a different recipe
- Mark processed records in source
- Search for records before adding
Trigger Condition to filter ‘good’ events
- Only select events that match a certain set of values
- Conditions can be a set of AND’s or OR’s. Can’t mix – Oh no!
- Express complex conditions as a formula (Example)
Query based filter (hidden)
- SOQL query for Salesforce
- Query for Quickbase
- Saved searches for NetSuite
Controlling the fields of interest (hidden)
- Field list to limit what gets pulled and passed down
Choosing between polling and web hooks
- Real-time is very important (Webhook)
- Very few events (Webhooks)
- Not super time critical and significant changes – Poll
Please send your questions and suggestions to firstname.lastname@example.org. Click here to register for an upcoming product hour