Actions
Actions are reusable operations you can include in test steps. They wrap provider APIs or internal logic with a typed interface.
Core ideas
- Schema-first: Each action defines name, description, input schema, and output schema.
- Auth integration: Actions can declare an auth provider (OAuth/API key) and required scopes; tokens are injected at runtime.
- Reusable: Define once, use across multiple tests and suites.
Where to manage
- Dashboard → Actions: Create/edit actions and set schemas.
- Dashboard → Action Library / Action Packs: Import prebuilt actions and curated packs.
Tips
- Keep input schemas minimal and validate at the edge; use enums for common choices.
- Use provider templates to prefill auth and base URLs.
- Test actions with the request step in your tests.
Last updated on