# geni workflow trigger-sample (/cli/resource/workflow/trigger-sample)



```sh
geni workflow trigger-sample [id] [flags]
```

Fetches a few real records from the workflow's configured poll trigger, so you see the exact shape `input` receives before writing `main.ts` or `instructions.md`. The cloud resolves the trigger's credential and source config and returns the payloads.

Wire the trigger's credential and input values with [`config set`](/cli/resource/config) first, and publish so the trigger exists in the database.

## Synopsis [#synopsis]

```sh
geni workflow trigger-sample
geni workflow trigger-sample wf_01HX --json
```

| Arg / Flag     | Notes                                           |
| -------------- | ----------------------------------------------- |
| `[id]`         | Workflow id. Omit to use the marker in `--dir`. |
| `--dir <path>` | Resource directory. Defaults to cwd.            |
| `--json`       | Machine-readable output.                        |

Find poll trigger providers with [`geni trigger list`](/cli/trigger/list).
