Learn from working projects
Examples organized by the problem they solve
The SolidActions examples repository contains complete workflow projects and focused SDK patterns. Use the smallest project that matches your problem, then replace its sample inputs and provider mappings deliberately.
Start with Hello World when you are validating setup.
It requires no third-party credentials. The calendar sync is an advanced integration example with provider access, several Variables, a tracking spreadsheet, and destructive synchronization behavior.
Case study: prevent double-booking across calendars
A consultant, agency owner, or operator may have separate Google Calendars for different businesses. Each calendar shows only part of that person's availability, so booking time in one can leave the others looking free. Manually copying and updating every event is repetitive and easy to miss.
The problem
Two calendars need to reflect the same busy time without inviting every attendee twice or relying on a person to maintain duplicate events.
The SolidActions approach
A scheduled workflow reads both calendars, creates or updates tagged copies in the other calendar, tracks source-to-copy IDs in Google Sheets, and removes tracked copies whose source event disappeared.
What the example demonstrates
| Product area | How the example uses it |
|---|---|
| Project | Packages the TypeScript source, YAML workflow definitions, build, and deployed environments. |
| Connections | Uses managed Google Calendar and Google Sheets authorizations instead of provider tokens in source. |
| Variables | Maps the two Connections plus calendar IDs, spreadsheet ID, prefixes, scan limits, and optional Telegram alert values. |
| Schedule | Runs the two-way sync every 15 minutes without a person or AI client staying online. |
| Webhook | Provides an on-demand sync entry point plus setup and integration-test workflows. |
| Runs | Records the fetch, create, update, tracking-sheet, deletion, and notification steps for each execution. |
Synchronization behavior
- Fetch events from Calendar A and Calendar B through the workflow Connection.
- Load the source-to-copy ledger from the configured Google Sheet.
- Create missing copies and update copies when an original event's tracked fields change.
- Skip tagged copies and cross-invited events so the workflow does not create an endless duplication loop.
- Delete a tracked copy when its original is no longer present in the configured scan window.
- Write the ledger changes and optionally send a Telegram alert when operations fail.
Synced copies carry a configurable title prefix and preserve useful context in their description. They do not copy the attendee list, which avoids sending duplicate invitations. Treat the original as the editable source; a later sync can replace changes made only to its managed copy.
Test this with noncritical calendars first.
The example creates, updates, and deletes calendar events. Its event limit and date window determine what the workflow considers present, so verify those settings and the Google Sheet ledger before enabling the schedule. The source builds successfully, but your provider permissions and current OAuth action catalog still require a real integration smoke test.
Open Google Calendar Sync on GitHub
More problems and examples
Prove the platform works end to end
Deploy and run a three-step greeting without configuring a third-party account.
Hello World →Wait for a human decision
Model an invoice approval that pauses durably until someone follows an approve or reject URL.
Invoice approval pattern →Recover from temporary failures
Use retry policies and durable steps for provider calls that may fail transiently.
Retry workflow pattern →Install tools the sandbox does not include
Add ffmpeg, Python packages, or build-time shell setup to a workflow's managed image.
Setup block tools →Coordinate parent and child work
Break a longer process into internal child workflows, messaging, parallel steps, and durable waits.
SDK feature patterns →Call an OAuth-backed API
Map a GitHub Connection and call a cataloged provider action without receiving the upstream access token.
OAuth workflow pattern →What the workflow examples do not cover yet
The repository currently focuses on deployed workflow code. Docs, Crews, Pegboards, and Dashboards are hosted workspace surfaces authored through the app or hosted MCP, so their public guides contain problem-led prompts rather than pretending a TypeScript workflow repository is an example of those products.
New to workflow code? Start with Build and deploy a workflow, then return to the example whose problem is closest to yours.