workato-connector-sdk-advanced
This skill should be used when the user asks about "connector planning", "code patterns", "defining schema", "best practices workato", "error handling workato", "connector architecture", "object_definitions patterns", "reusable methods", or needs advanced guidance for building production-quality Workato connectors.
What this skill does
# Workato SDK Advanced Patterns
Guide for advanced connector development patterns, architecture planning, and best practices.
## Overview
Building production-quality connectors requires:
- Thoughtful planning and API analysis
- Reusable code patterns
- Proper schema design
- Robust error handling
- Performance optimization
## Connector Planning
### API Analysis Checklist
Before building a connector, analyze:
1. **Authentication**
- What auth method does the API use?
- Are there multiple auth options?
- How are tokens refreshed?
2. **Data Model**
- What are the primary objects/resources?
- How do objects relate to each other?
- What fields are required vs optional?
3. **Operations**
- What CRUD operations are available?
- Are there batch operations?
- What search/filter capabilities exist?
4. **Webhooks/Events**
- Does the API support webhooks?
- What events are available?
- How is webhook security handled?
5. **Rate Limits**
- What are the rate limits?
- How should the connector handle throttling?
### Connector Structure
Organize connector code logically:
```ruby
{
title: 'My Connector',
# 1. Connection & Auth
connection: { ... },
# 2. Reusable Methods
methods: { ... },
# 3. Object Definitions (Schemas)
object_definitions: { ... },
# 4. Pick Lists
pick_lists: { ... },
# 5. Actions
actions: { ... },
# 6. Triggers
triggers: { ... },
# 7. Streams (if needed)
streams: { ... }
}
```
## Code Patterns
### Reusable Methods
Extract common logic into methods:
```ruby
methods: {
# Pagination helper
paginate: lambda do |endpoint, params = {}|
results = []
page = 1
loop do
response = get(endpoint).params(params.merge(page: page, per_page: 100))
results.concat(response['items'])
break unless response['has_more']
page += 1
end
results
end,
# Error handling wrapper
safe_request: lambda do |&block|
block.call
.after_error_response(/4\d{2}/) do |code, body, headers, message|
error("API Error (#{code}): #{body['error'] || message}")
end
.after_error_response(/5\d{2}/) do |code, body, headers, message|
error("Server Error (#{code}): Please try again later")
end
end,
# Field mapping
map_fields: lambda do |record, field_map|
field_map.each_with_object({}) do |(api_field, workato_field), result|
result[workato_field] = record[api_field] if record[api_field]
end
end
}
```
### Using Methods
```ruby
execute: lambda do |connection, input|
records = call('paginate', '/api/records', { status: 'active' })
records.map { |r| call('map_fields', r, { 'id' => 'record_id', 'name' => 'title' }) }
end
```
## Schema Design
### Object Definitions
Define reusable schemas:
```ruby
object_definitions: {
# Base record schema
record: {
fields: lambda do |connection, config_fields|
[
{ name: 'id', label: 'Record ID' },
{ name: 'name', label: 'Name' },
{ name: 'created_at', label: 'Created At', type: 'date_time' },
{ name: 'updated_at', label: 'Updated At', type: 'date_time' }
]
end
},
# Input-specific schema (writable fields only)
record_input: {
fields: lambda do |connection, config_fields|
[
{ name: 'name', label: 'Name', optional: false },
{ name: 'email', label: 'Email', control_type: 'email' },
{ name: 'status', control_type: 'select', pick_list: 'statuses' }
]
end
},
# Dynamic schema based on config
dynamic_record: {
fields: lambda do |connection, config_fields|
object_type = config_fields['object_type']
get("/api/schemas/#{object_type}")['fields'].map do |field|
{
name: field['name'],
label: field['label'],
type: field['type'],
optional: !field['required']
}
end
end
}
}
```
### Schema Composition
Combine schemas:
```ruby
input_fields: lambda do |object_definitions|
[
{ name: 'id', optional: false }
].concat(object_definitions['record_input'])
end
```
## Error Handling
### Comprehensive Error Handling
```ruby
execute: lambda do |connection, input|
post('/api/records')
.payload(input)
.after_error_response(400) do |code, body, headers, message|
# Validation errors
errors = body['errors']&.map { |e| e['message'] }&.join(', ')
error("Validation failed: #{errors || body['message']}")
end
.after_error_response(401) do |code, body, headers, message|
error("Authentication failed. Please reconnect.")
end
.after_error_response(403) do |code, body, headers, message|
error("Permission denied: #{body['message']}")
end
.after_error_response(404) do |code, body, headers, message|
error("Resource not found")
end
.after_error_response(429) do |code, body, headers, message|
retry_after = headers['Retry-After']
error("Rate limited. Retry after #{retry_after} seconds")
end
.after_error_response(/5\d{2}/) do |code, body, headers, message|
error("Server error (#{code}). Please try again later.")
end
end
```
### Retry Logic
```ruby
actions: {
create_with_retry: {
execute: lambda do |connection, input|
post('/api/records').payload(input)
end,
retry_on_response: [429, 503],
max_retries: 3
}
}
```
## Best Practices
### Naming Conventions
- **Actions**: Verb + noun (`create_record`, `search_contacts`)
- **Triggers**: `new_` prefix (`new_record`, `new_event`)
- **Fields**: snake_case matching API where possible
### Performance
1. **Minimize API calls** - Batch requests when possible
2. **Use pagination** - Don't fetch all records at once
3. **Cache static data** - Store picklist values
4. **Optimize webhooks** - Use webhooks over polling when available
### Security
1. **Never log credentials** - Use `control_type: 'password'`
2. **Validate webhooks** - Always verify signatures
3. **Sanitize inputs** - Escape user data in URLs
4. **Use HTTPS** - Never allow HTTP connections
### User Experience
1. **Clear labels** - Use descriptive field names
2. **Helpful hints** - Explain what fields do
3. **Smart defaults** - Pre-populate common values
4. **Validation** - Catch errors before API calls
## Debugging
### Local Testing
```ruby
# Add debug output
execute: lambda do |connection, input|
workato.log("Input: #{input.inspect}")
response = get('/api/records')
workato.log("Response: #{response.inspect}")
response
end
```
### Common Issues
| Issue | Cause | Solution |
|-------|-------|----------|
| "undefined method" | Method not defined | Check method name spelling |
| Empty response | Wrong endpoint/params | Log request, check API docs |
| Auth fails | Token expired | Implement token refresh |
| Missing fields | Schema mismatch | Update object_definitions |
## Reference Files
For detailed documentation:
### Connector Guide
- **`references/guides__advanced-connector-guide__introduction.md`** - Guide overview
- **`references/guides__advanced-connector-guide__connector-planning.md`** - Planning checklist
- **`references/guides__advanced-connector-guide__connector-building-defining-schema.md`** - Schema design
- **`references/guides__advanced-connector-guide__connector-building-building-actions.md`** - Action patterns
- **`references/guides__advanced-connector-guide__connector-building-building-triggers.md`** - Trigger patterns
- **`references/guides__advanced-connector-guide__connector-building-code-patterns.md`** - Code patterns
### Best Practices
- **`references/guides__best-practices.md`** - General best practices
- **`references/guides__error-handling.md`** - Error handling patterns
- **`references/guides__debugging.md`** - Debugging techniques
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.