​

Automations

Automations let Gina repeat a task without a new chat request each time. A recipe defines the work; a schedule or supported webhook determines when it runs. Creation and scheduling availability depend on your account. Automations in the Gina web app, captured September 7, 2026. Statuses and run counts are shown as captured.

• Recipes: build and test a reusable task.
• Schedules: choose a cadence and monitor runs.
• Webhooks: respond to supported events and inspect triggers.
• Copy trading: review a trader and configure supported automated execution.

​

Create and test

1. Choose Create in the sidebar.
2. Ask “Each weekday at 9 AM Europe/London, summarize BTC and ETH market changes with sources. Do not trade.”
3. Review the workflow and inputs. Confirm it performs only the intended research.
4. Keep Simulated mode enabled and choose Run.
5. Inspect step statuses and output; correct failures before scheduling.

Actual Create component in Storybook. Simulated runs can use live data while simulating side effects. Run Live may perform real actions; do not use live trading as an onboarding test. Sample result illustrating live-run labels; no workflow was executed for this screenshot.

​

Schedule and monitor

Choose Schedule, select a suggested cadence or enter a custom one, and check its time zone. The panel uses Schedule workflow now or Apply custom cadence. Review the resulting schedule. Open Automations to inspect configured work and runs. Accepted can mean queued, not completed. Runs may be late or fail because of data, limits, or timeouts.

​

Recipes and webhooks

Use the recipe’s own trigger configuration for supported webhooks. Its event, signature, and payload must match; there is no universal payload. Never put secrets in prompts or payloads. Avoid relying on a run when failure could cause harm. Gina Read only inspects schedules; changes require write access. Account Memory differs from MCP /workspace. Related: Research, Safety, Product Guide.