# Events

Events let you customize what Finqu does when something happens in a store. A sale, a new customer, or a cron schedule can trigger a [Worker](./workers) with custom instructions or start a [Playbook](./playbooks).

Merchants configure Events in **Work Hub**. Partners can help them define instructions and workflows that respond to the way their business operates.

## How Events work

An Event connects a trigger to a configured action:

| Part | Purpose |
|---|---|
| Trigger | The store activity or cron schedule that starts the work |
| Worker or Playbook | The agent or sequence of steps that performs the work |
| Instructions | The task and desired outcome for a Worker, or the steps already defined in a Playbook |

Choose a **Worker** when you want an agent to perform a task using custom instructions. Choose a **Playbook** when the response needs an ordered sequence of steps, potentially assigned to different Workers.

Workers use the tools and store context configured for them. [MCP Tools](./mcp-tools) connect external services, while [Guidelines](./guidelines) shape agent behavior.

## Example configurations

These examples illustrate behavior you can configure; they are not enabled automatically.

| When | Run | Example instructions or workflow |
|---|---|---|
| A sale happens | A Worker | Review the sale and summarize anything that needs attention |
| A new customer joins | A Playbook | Carry out the store's defined new-customer workflow |
| A cron schedule runs | The Analyst | Prepare a daily summary of store activity |

Both Workers and Playbooks can be triggered by Events. The examples above are starting points, not fixed trigger-to-action pairings.

## Configure behavior in Work Hub

1. Decide which store change or schedule should start the work.
2. Configure the Event in Work Hub with that trigger.
3. Choose a Worker and give it custom instructions, or select the Playbook that defines the workflow.
4. Review the tools, context, and instructions available to the Workers involved.
5. Check the behavior with a representative scenario before relying on it for routine operations.

Keep instructions specific: describe what to inspect, which action to take, and the expected result. For a multi-step response, put the steps in a Playbook so the same workflow can be reused.

## Events and other ways to run work

- **Events** start configured work in response to store activity or a cron schedule.
- **Manual and bulk actions** let merchants run Playbooks directly when needed.
- **Webhooks** deliver store notifications to an external application's endpoint. See [Webhooks](/apis-and-tools/rest-api/webhooks) when you need to react in your own service.

## Next steps

- [Workers](./workers) — Choose an agent and customize its instructions
- [Playbooks](./playbooks) — Define a repeatable sequence of Worker tasks
- [MCP Tools](./mcp-tools) — Connect the services your Workers need
- [Guidelines](./guidelines) — Set shared instructions for agent behavior