automations-developer

Build and debug Skedulo Pulse automations with REST JSON and Step Functions workflows.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/skeduloDevelopers/agent-skills --skill automations-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: automations-developer
Source: https://github.com/skeduloDevelopers/agent-skills/tree/main/skills/automations-developer
Command: npx skills add https://github.com/skeduloDevelopers/agent-skills --skill automations-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you create, edit, and deploy Skedulo Pulse automations when the JSON schema, trigger/action vocabulary, and JSONata Step Functions quirks cause errors or broken behavior.

Core Features & Use Cases

  • Automation authoring with the correct REST payload shape for POST/PUT to the automation-service, including triggers, workflow.definition, and status handling.
  • Trigger and action vocabulary guidance for objectModified automations, including how to craft non-empty filters and choose valid actions via /automations/actions or the OpenAPI surface.
  • Debugging for 400/500 automation-service failures by applying a documented checklist of required schema/resource/JSONata fixes that make automations load successfully.
  • Workflow construction patterns using Step Functions ASL with Choice branching and JSONata expressions referencing $trigger.current/$trigger.previous and task results.

Quick Start

Ask the skill to generate a disabled automation JSON for a Jobs Update trigger that filters on UID != null and posts selected fields to an external HTTPS endpoint using the http action, including the JSONata variables and the correct action resource format.

Frequently Asked Questions about automations-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Skedulo Pulse automation with the correct REST JSON payload?

To build a Skedulo Pulse automation, you must structure the REST JSON payload for POST/PUT to the automation-service, including trigger definitions, workflow.definition, and status handling. Correct action resource prefixes and $trigger data referencing are required for deployment.

Why does my Skedulo Pulse automation return a 400 or 500 error on load?

Skedulo Pulse automation 400 or 500 runtime failures usually stem from incorrect schema structure or invalid JSONata expressions. You can resolve these by applying a nine-item schema correction checklist covering resource prefixes, JSONata escaping constraints, and workflow patterns.

How do I use JSONata expressions in Skedulo Step Functions workflows?

JSONata expressions in Skedulo Step Functions workflows reference $trigger.current, $trigger.previous, and task results. You must follow specific JSONata block and escaping constraints to ensure the automation loads and runs without failures.

Can I trigger a Skedulo automation when an object is modified?

Yes, you can trigger a Skedulo automation when an object is modified using objectModified triggers. You need to craft non-empty filters for the trigger and select valid actions via the /automations/actions endpoint or the OpenAPI surface.

What is the best way to debug a broken Skedulo Pulse automation workflow?

The best way to debug a broken Skedulo Pulse automation workflow is to apply a documented checklist of required schema, resource, and JSONata fixes. This resolves load and runtime failures by ensuring correct workflow definition and JSONata-safe patterns.

How do I post data to an external HTTPS endpoint from a Skedulo automation?

To post data to an external HTTPS endpoint from a Skedulo automation, configure an objectModified trigger with a filter like UID != null, then use the http action with the correct action resource format and JSONata variables to send selected fields.