workato-connector-sdk-triggers
This skill should be used when the user asks about "build trigger", "webhook trigger", "poll trigger", "dynamic webhook", "static webhook", "hybrid trigger", "dedup", "trigger_limit", "closure", or needs to implement triggers for a Workato custom connector.
What this skill does
# Workato SDK Triggers
Guide for building triggers in Workato custom connectors. Triggers start recipes when new data is available.
## Overview
Workato supports three trigger types:
1. **Poll triggers** - Periodically check for new records
2. **Webhook triggers** - Receive real-time push notifications
3. **Hybrid triggers** - Combine polling with webhooks
## Trigger Structure
```ruby
triggers: {
new_record: {
title: 'New record',
subtitle: 'Triggers when a new record is created',
description: lambda do |input, pick_list_label|
"New <span class='provider'>#{pick_list_label['object_type'] || 'record'}</span>"
end,
input_fields: lambda do
[
{ name: 'object_type', control_type: 'select', pick_list: 'object_types' }
]
end,
poll: lambda do |connection, input, closure|
# Polling logic
end,
dedup: lambda do |record|
record['id']
end,
output_fields: lambda do |object_definitions|
object_definitions['record']
end
}
}
```
## Poll Triggers
Periodically fetch new records.
### Basic Poll Trigger
```ruby
new_record: {
title: 'New record',
input_fields: lambda do
[{ name: 'since', type: 'date_time', optional: true }]
end,
poll: lambda do |connection, input, closure|
# closure persists between polls
since = closure || input['since'] || Time.now.iso8601
records = get('/api/records')
.params(created_after: since, order: 'created_at')['items']
next_since = records.last&.[]('created_at') || since
{
events: records,
next_poll: next_since, # Stored in closure for next poll
can_poll_more: records.size >= 100
}
end,
dedup: lambda do |record|
record['id'] # Unique identifier for deduplication
end,
output_fields: lambda do
[
{ name: 'id' },
{ name: 'name' },
{ name: 'created_at', type: 'date_time' }
]
end
}
```
### Closure Usage
The `closure` parameter persists state between polls:
```ruby
poll: lambda do |connection, input, closure|
closure ||= { page_token: nil, since: input['since'] }
response = get('/api/records').params(
since: closure['since'],
page_token: closure['page_token']
)
{
events: response['items'],
next_poll: {
since: response['items'].last&.[]('created_at') || closure['since'],
page_token: response['next_page_token']
},
can_poll_more: response['has_more']
}
end
```
## Webhook Triggers
Receive real-time notifications from the API.
### Static Webhook
Webhook URL is fixed per connection:
```ruby
new_event_webhook: {
title: 'New event (webhook)',
webhook_subscribe: lambda do |connection, input, webhook_url|
post('/api/webhooks').payload(
url: webhook_url,
events: ['record.created']
)
end,
webhook_unsubscribe: lambda do |connection, webhook|
delete("/api/webhooks/#{webhook['id']}")
end,
webhook_notification: lambda do |connection, input, payload|
payload['data'] # Return the event data
end,
dedup: lambda do |event|
event['id']
end,
output_fields: lambda do
[{ name: 'id' }, { name: 'type' }, { name: 'data', type: 'object' }]
end
}
```
### Dynamic Webhook
Webhook URL changes per recipe:
```ruby
new_event_dynamic: {
title: 'New event (real-time)',
webhook_subscribe: lambda do |connection, input, recipe_id, webhook_url|
post('/api/webhooks').payload(
url: webhook_url,
events: input['event_types'],
metadata: { recipe_id: recipe_id }
)
end,
webhook_unsubscribe: lambda do |connection, webhook|
delete("/api/webhooks/#{webhook['id']}")
end,
webhook_notification: lambda do |connection, input, payload, headers|
# Verify webhook signature
signature = headers['X-Webhook-Signature']
expected = workato.hmac_sha256(payload.to_json, connection['webhook_secret'])
error('Invalid signature') unless signature == expected
payload['events']
end,
dedup: lambda do |event|
event['event_id']
end
}
```
## Hybrid Triggers
Combine polling for historical data with webhooks for real-time:
```ruby
new_record_hybrid: {
title: 'New record (real-time)',
# Poll for historical/missed records
poll: lambda do |connection, input, closure|
since = closure || input['since'] || Time.now.iso8601
records = get('/api/records').params(created_after: since)['items']
{
events: records,
next_poll: records.last&.[]('created_at') || since,
can_poll_more: records.size >= 100
}
end,
# Subscribe to webhook for real-time
webhook_subscribe: lambda do |connection, input, recipe_id, webhook_url|
post('/api/webhooks').payload(url: webhook_url, events: ['record.created'])
end,
webhook_unsubscribe: lambda do |connection, webhook|
delete("/api/webhooks/#{webhook['id']}")
end,
webhook_notification: lambda do |connection, input, payload|
[payload['record']] # Return as array
end,
dedup: lambda do |record|
record['id']
end
}
```
## Deduplication
The `dedup` lambda returns a unique identifier to prevent duplicate processing:
```ruby
# Simple ID dedup
dedup: lambda do |record|
record['id']
end
# Composite dedup
dedup: lambda do |record|
"#{record['type']}_#{record['id']}_#{record['version']}"
end
```
## Webhook Security
### Signature Verification
```ruby
webhook_notification: lambda do |connection, input, payload, headers|
# HMAC verification
signature = headers['X-Signature']
computed = workato.hmac_sha256(payload.to_json, connection['secret'])
error('Invalid webhook signature') unless signature == computed
payload['data']
end
```
### IP Allowlisting
Some APIs require allowlisting Workato's IPs. Refer to Workato documentation for current IP ranges.
## Trigger Limits
For APIs that don't track "since" timestamps:
```ruby
new_record: {
poll: lambda do |connection, input, closure|
records = get('/api/records').params(limit: 100)['items']
{
events: records.first(workato.trigger_limit || 100),
can_poll_more: false
}
end
}
```
## Sample Output
Provide sample data for recipe building:
```ruby
sample_output: lambda do |connection, input|
get('/api/records').params(limit: 1)['items'].first || {
id: 'sample_123',
name: 'Sample Record',
created_at: Time.now.iso8601
}
end
```
## Reference Files
For detailed documentation:
### Trigger Types
- **`references/guides__building-triggers.md`** - Triggers overview
- **`references/guides__building-triggers__poll.md`** - Poll trigger patterns
- **`references/guides__building-triggers__static-webhook.md`** - Static webhooks
- **`references/guides__building-triggers__dynamic-webhook.md`** - Dynamic webhooks
- **`references/guides__building-triggers__hybrid-triggers.md`** - Hybrid triggers
### Webhook Security
- **`references/guides__building-triggers__securing-webhooks.md`** - Webhook security
### Limits
- **`references/guides__trigger-limit.md`** - Trigger limits and quotas
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.