# Customizing Init Scripts

## Background

The per-workflow configure script has been removed. Use the workflow `init` script as the established location to run Stoobly commands and shell commands before a service workflow runs. Uses include, but are not limited to:

1. Building source files
2. Building fixtures to use for mocking
3. Applying Stoobly rules (rewrite, match, filter)

To learn more where it is used, see:

{% content-ref url="/pages/kGz1rovOOBYXXhoOcn3E" %}
[Workflow](/core-concepts/scaffold/workflow.md)
{% endcontent-ref %}

## Customizing

1. Each workflow provides an `init` script that runs during workflow startup
2. It can be accessed in the following location:

```bash
.stoobly/services/<SERVICE-NAME>/<WORKFLOW-NAME>/init
```

3. Add any Stoobly configuration commands and setup logic to this file
4. Modifications to this file will not be overriten when the `service create` command is re-run.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stoobly.com/guides/how-to-integrate-e2e-testing/how-to-scaffold-an-app/customizing-a-workflow/customizing-init-scripts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.