To configure the bootstrap workflow according to your needs, you’ll need to provide a few things.

- A profile for each partner (sender and receiver).
- A partnership linking the two partners and defining the relationship between them.
- A lookup entry for each partner that maps their EDI identifiers to their profile.

In the following steps, we’ll take care of all of these.

## Update your profile

<TODO>
  The following instructions assume you only use one set of IDs with all your trading partners, however if you need different IDs for different partners, you need multiple profiles for yourself. That’s a detail we’ll leave out to get the first version of this page out. We’ll add it later. See [this Slack conversation](https://stedi-inc.slack.com/archives/C03V2DMGH8Q/p1673868098255189) for details.
</TODO>

In the following instructions, you’ll need to replace values between `<` and `>` with the values that are relevant to your trading partner.

| Value                  | Description |
| ---------------------- | ----------- |
| YOUR_NAME              | The name of your business. This is only used for display purposes and is not included in EDI messages. |
| ACKNOWLEDGMENT_REQUEST | Indicates if you want to receive [TA1 acknowledgments](https://www.stedi.com/edi/x12/segment/TA1) in response to EDI messages your trading partner sends. Corresponds to ISA-14. [See the list of possible values.](https://www.stedi.com/edi/x12/element/I13) |
| GS_APPLICATION_ID      | Identifies you in [GS segments](https://www.stedi.com/edi/x12/segment/GS). Corresponds to GS-02, if you’re the sender, or to GS-03, if you’re the receiver. May be equal to ISA_ID. |
| ISA_ID                 | Identifies you in [ISA segments](https://www.stedi.com/edi/x12/segment/ISA). Corresponds to ISA-06, if you’re the sender, or to ISA-08, if you’re the receiver. |
| ID_QUALIFIER           | The type of ID used in ISA_ID, e.g. DUNS number, Health Industry Number, or custom number. Corresponds to ISA-05, if you’re the sender, or to ISA-07, if you’re the receiver. [See the list of possible values.](https://www.stedi.com/edi/x12/element/I05) |


1. Using the Stedi UI, go to [Stash](https://www.stedi.com/app/stash).
2. Open the keyspace called [partners-configuration](https://www.stedi.com/app/stash/keyspace/partners-configuration).
3. Edit the key called `profile|this-is-me` and change the value to the following:

```json
{
  "acknowledgmentRequestedCode": "<ACKNOWLEDGMENT_REQUEST>",
  "id": "this-is-me",
  "partnerApplicationId": "<GS_APPLICATION_ID>",
  "partnerInterchangeId": "<ISA_ID>",
  "partnerInterchangeQualifier": "<ID_QUALIFIER>",
  "partnerName": "<YOUR_NAME>"
}
```

## Add a trading partner profile

In the following instructions, you’ll need to replace values between `<` and `>` with the values that are relevant to your trading partner.

| Value                  | Description |
| ---------------------- | ----------- |
| WORKFLOW_PARTNER_ID    | The unique ID you want to assign to your trading partner. This ID is used by the bootstrap workflow. It’s not used in EDI messages. |
| PARTNER_NAME           | The display name of your trading partner. This is for your convenience and is not included in EDI messages. |
| ACKNOWLEDGMENT_REQUEST | Indicates if your trading partner wants to receive [TA1 acknowledgments](https://www.stedi.com/edi/x12/segment/TA1) in response to EDI messages you send. Corresponds to ISA-14. [See the list of possible values.](https://www.stedi.com/edi/x12/element/I13) |
| GS_APPLICATION_ID      | Identifies your trading partner in [GS segments](https://www.stedi.com/edi/x12/segment/GS). Corresponds to GS-02, if your trading partner is the sender, or to GS-03, if your trading partner is the receiver. May be equal to ISA_PARTNER_ID. |
| ISA_PARTNER_ID         | Identifies your trading partner in [ISA segments](https://www.stedi.com/edi/x12/segment/ISA). Corresponds to ISA-06, if your trading partner is the sender, or to ISA-08, if your trading partner is the receiver. |
| PARTNER_ID_QUALIFIER   | The type of ID used in ISA_PARTNER_ID, e.g. DUNS number, Health Industry Number, or custom number. Corresponds to ISA-05, if your trading partner is the sender, or to ISA-07, if your trading partner is the receiver. [See the list of possible values.](https://www.stedi.com/edi/x12/element/I05) |
| SEND_DESCRIPTION       | A description that tells you what type of document you’re sending to whom. This is for your convenience and is not included in EDI messages. |
| SEND_GUIDE_ID          | The Stedi guide you want to use to create outbound EDI messages. |
| BUCKET_NAME            | The name of the bucket where outbound messages are stored. Your trading partner can pick up your EDI messages here. |
| USAGE_INDICATOR_CODE   | Indicates if messages are test messages or production messages. Corresponds to ISA-15. [See the list of possible values](https://www.stedi.com/edi/x12/element/I14). |
| RECEIVE_DESCRIPTION    | A description that tells you what type of document you’re receiving from whom. This is for your convenience and is not included in EDI messages. |
| DESTINATION_URL        | The URL of your trading partner’s API endpoint. The workflow will send EDI messages there. |
| RECEIVE_GUIDE_ID       | The Stedi guide you want to use to parse and validate inbound EDI messages. |


1. Using the Stedi UI, go to [Stash](https://www.stedi.com/app/stash).
2. Open the keyspace called [partners-configuration](https://www.stedi.com/app/stash/keyspace/partners-configuration).
3. Add a key called `profile|<WORKFLOW_PARTNER_ID>` with the following value:

```json
{
  "acknowledgmentRequestedCode": "<ACKNOWLEDGMENT_REQUEST>",
  "id": "<WORKFLOW_PARTNER_ID>",
  "partnerApplicationId": "<GS_APPLICATION_ID>",
  "partnerInterchangeId": "<ISA_PARTNER_ID>",
  "partnerInterchangeQualifier": "<PARTNER_ID_QUALIFIER>",
  "partnerName": "<PARTNER_NAME>"
}
```

4. Add a key called `lookup|ISA|<PARTNER_ID_QUALIFIER>/<ISA_PARTNER_ID>` with the following value:

```json
{
  "partnerId": "<WORKFLOW_PARTNER_ID>"
}
```

5. Add a key called `partnership|this-is-me|<WORKFLOW_PARTNER_ID>` with the following value:

<TODO>
  The following example assumes messages are received in a bucket and sent to a webhook. That’s not necessarily the case. At a later point, we’ll add instructions on how to change this, but this simplified example is good enough to get a first version of this page out.
</TODO>

```json
{
  "transactionSets": [
    {
      "description": "<SEND_DESCRIPTION>",
      "destinations": [
        {
          "destination": {
            "bucketName": "<BUCKET_NAME>",
            "path": "trading_partners/<WORKFLOW_PARTNER_ID>/outbound",
            "type": "bucket"
          }
        }
      ],
      "guideId": "<SEND_GUIDE_ID>",
      "receivingPartnerId": "<WORKFLOW_PARTNER_ID>",
      "sendingPartnerId": "this-is-me",
      "usageIndicatorCode": "<USAGE_INDICATOR_CODE>"
    },
    {
      "description": "<RECEIVE_DESCRIPTION>",
      "destinations": [
        {
          "destination": {
            "type": "webhook",
            "url": "<DESTINATION_URL>"
          }
        }
      ],
      "guideId": "<RECEIVE_GUIDE_ID>",
      "receivingPartnerId": "this-is-me",
      "sendingPartnerId": "<WORKFLOW_PARTNER_ID>",
      "usageIndicatorCode": "<USAGE_INDICATOR_CODE>"
    }
  ]
}
```

## Map inbound messages

You can use [Stedi Mappings](https://www.stedi.com/docs/mappings) to translate inbound EDI messages to a custom JSON shape. The bootstrap workflow can automatically apply the mapping to any inbound message. You just need to provide it with the ID of your mapping.

1. Using the Stedi UI, go to [Stash](https://www.stedi.com/app/stash).
2. Open the keyspace called [partners-configuration](https://www.stedi.com/app/stash/keyspace/partners-configuration).
3. Edit the partnership that has the configuration for the inbound messages.
4. In the value for that configuration, find the transaction set related to messages you receive. (The one where `receivingPartnerId` is `this-is-me`.)
5. Add a key `mappingId` with the value set to your mapping ID. Add it to the object inside the `destinations` array on the same level as the key `destination`. For example:

```json
{
  "transactionSets": [
    {
      "description": "Purchase Orders sent to ANOTHERMERCH",
      "destinations": [
        {
          "destination": {
            "bucketName": "e97e59c8-d5d4-4dde-97ab-52cdf777eaf5-sftp",
            "path": "trading_partners/ANOTHERMERCH/outbound",
            "type": "bucket"
          }
        }
      ],
      "guideId": "01GPNS4BZ7FSZRTEM7HY5921VH",
      "receivingPartnerId": "another-merchant",
      "sendingPartnerId": "this-is-me",
      "usageIndicatorCode": "T"
    },
    {
      "description": "Purchase Order Acknowledgements received from ANOTHERMERCH",
      "destinations": [
        {
          "destination": {
            "type": "webhook",
            "url": "https://webhook.site/f2b6d098-faba-488f-af8d-c4a9c5bf5c0a"
          },
          "mappingId": "01GPXEHSDA5VY0GWMYM74HZP3H"
        }
      ],
      "guideId": "01GPNS4DB4CY1744P9GXK1NM50",
      "receivingPartnerId": "this-is-me",
      "sendingPartnerId": "another-merchant",
      "usageIndicatorCode": "T"
    }
  ]
}
```

## Map outbound messages

You can use [Stedi Mappings](https://www.stedi.com/docs/mappings) to translate custom JSON shapes to a outbound EDI messages. The bootstrap workflow can automatically apply the mapping to any outbound message. You just need to provide it with the ID of your mapping.

1. Using the Stedi UI, go to [Stash](https://www.stedi.com/app/stash).
2. Open the keyspace called [partners-configuration](https://www.stedi.com/app/stash/keyspace/partners-configuration).
3. Edit the partnership that has the configuration for the outbound messages.
4. In the value for that configuration, find the transaction set related to messages you send. (The one where `sendingPartnerId` is `this-is-me`.)
5. Add a key `mappingId` with the value set to your mapping ID. Add it to the object inside the `destinations` array on the same level as the key `destination`. For example:

```json
{
  "transactionSets": [
    {
      "description": "Purchase Orders sent to ANOTHERMERCH",
      "destinations": [
        {
          "destination": {
            "bucketName": "e97e59c8-d5d4-4dde-97ab-52cdf777eaf5-sftp",
            "path": "trading_partners/ANOTHERMERCH/outbound",
            "type": "bucket"
          },
          "mappingId": "01GPXEHSDA5VY0GWMYM74HZP3H"
        }
      ],
      "guideId": "01GPNS4BZ7FSZRTEM7HY5921VH",
      "receivingPartnerId": "another-merchant",
      "sendingPartnerId": "this-is-me",
      "usageIndicatorCode": "T"
    },
    {
      "description": "Purchase Order Acknowledgements received from ANOTHERMERCH",
      "destinations": [
        {
          "destination": {
            "type": "webhook",
            "url": "https://webhook.site/f2b6d098-faba-488f-af8d-c4a9c5bf5c0a"
          }
        }
      ],
      "guideId": "01GPNS4DB4CY1744P9GXK1NM50",
      "receivingPartnerId": "this-is-me",
      "sendingPartnerId": "another-merchant",
      "usageIndicatorCode": "T"
    }
  ]
}
```

## Sending and receiving documents with SFTP

The bootstrap repository reads inbound messages from the SFTP bucket and it writes outbound messages to SFTP. However, it doesn’t set up any SFTP users for you. You’ll need to create a user for each of your trading partners and send them the credentials. You can do so using the [Stedi SFTP UI](https://www.stedi.com/app/sftp).

Any inbound message is automatically processed by the bootstrap workflow, as we discussed before. When the bootstrap workflow writes an outbound message to SFTP, it considers its work done. However, your trading partner still needs to pick up the message, so be sure to tell them to [check the SFTP endpoint regularly](https://www.stedi.com/docs/sftp/polling).

Adjust the bootstrap workflow to the needs of your business. Add trading partners, guides, mappings, SFTP, AS2.

Adjusting the workflow

Adjusting the bootstrap workflow


The bootstrap workflow kicks in as soon as your trading partner uploads an EDI document with SFTP. But hold on, there’s a piece missing. Where does the SFTP come from and where are those documents stored? Well, the bootstrap workflow makes an assumption here: it assumes you’re using [Stedi SFTP](https://www.stedi.com/docs/sftp). With Stedi SFTP you get access to an SFTP endpoint that’s hosted by Stedi. You can create a user for your trading partners, send them the credentials, and they can use those to upload documents.

Stedi SFTP provides an endpoint, but it doesn’t provide storage. It leaves that task up to Stedi Buckets. In other words, there’s a dedicated bucket in your Stedi account that SFTP uses to write to and read from.

And this is where the bootstrap workflow picks things up. [Stedi Buckets](https://www.stedi.com/docs/buckets) has a feature called bucket notifications. A bucket notification fires off an event every time a document is written to the bucket. When you deploy the bootstrap workflow, it sets up a listener for that bucket notification and that listener kicks off a bit of code for every document that arrives. That code needs a place to run. That’s where [Stedi Functions](https://www.stedi.com/docs/functions) comes in.

Stedi Functions allows you to run a piece of code on the Stedi platform. That piece of code is called a function, but you probably already guessed that. A Stedi function has access to all the resources in your Stedi account, so it’s ideal for coordinating a workflow across Stedi products. That’s how the bootstrap workflow works: it deploys a function that knows how to process an EDI message.

## Receiving EDI

The [inbound](https://github.com/Stedi-Demos/bootstrap/tree/main/src/functions/edi/inbound) function performs the following steps.

1. It extracts the sender ID (ISA-06) and the receiver ID (ISA-08) from the EDI message.
2. Based on those IDs, it retrieves the partnership information related to those two trading partners.

The partnership information is stored in [Stedi Stash](https://www.stedi.com/docs/stash). One of the things the partnership information contains, is an ID for a Stedi guide. The Stedi guide is an EDI implementation guide: it describes exactly what the EDI message should look like.

3. The workflow sends the EDI message and the Stedi guide to [EDI Translate](https://www.stedi.com/docs/edi-translate), which validates the EDI message and translates it to JSON.

The partnership information may also contain an ID for [Stedi Mappings](https://www.stedi.com/docs/mappings). The shape of the JSON produced by EDI Translate is based closely on the EDI message. If you want to send the message to an API, it will need to be in a JSON shape the API can understand. Stedi Mappings can do that translation for you.

4. If the partnership information contains a mapping ID, the workflow will send the EDI message to Stedi Mappings.
5. The workflow will deliver the result to a destination configured in the partnership. The destination can either be a Stedi bucket or a webhook. The webhook can be any API endpoint; it doesn’t have to be related to Stedi.

## Sending EDI

The bootstrap workflow can also send EDI messages. It has a function called [outbound](https://github.com/Stedi-Demos/bootstrap/tree/main/src/functions/edi/outbound) that does that. The function doesn’t trigger automatically. Instead, you can call it automatically from your own, internal system. Or you can call it manually using the [Stedi CLI](https://www.npmjs.com/package/@stedi/cli). When you call the function, you need to pass in a JSON object containing a sending partner ID, a receiving partner ID, and a payload. [There’s an example in the bootstrap repository.](https://github.com/Stedi-Demos/bootstrap/blob/main/src/resources/X12/5010/850/outbound.json)

Here’s what the function does.

1. Based on the sender partner ID passed to the function, it gets the partner profile for the sender from [Stedi Stash](https://www.stedi.com/docs/stash).
2. Based on the receiving partner ID passed to the function, it gets the partner profile for the receiver from Stedi Stash.
3. It gets the partnership information for the sender and receiver from Stedi Stash.

As with inbound messages, the partnership information contains a Stedi guide ID and, optionally, a Stedi mapping ID. The Stedi mapping takes a custom JSON shape and translates it into JSON that resembles the shape of EDI. The Stedi guide describes exactly what that EDI shape needs to be.

4. The workflow generates control numbers required in the [ISA](https://www.stedi.com/edi/x12/segment/ISA), [GS](https://www.stedi.com/edi/x12/segment/GS), and [ST](https://www.stedi.com/edi/x12/segment/ST) segments of the EDI message. Control numbers for ISA and GS need to be unique across messages, so the workflow uses Stedi Stash to keep track of them. If you’re new to control numbers and you would like to know more, check out [our blog article about control numbers](https://www.stedi.com/blog/control-numbers-in-x12-edi).

5. Using the generated control numbers, the partner profiles, and the partnership information, the workflow constructs the ISA and GS envelopes.
6. If the partnership information contains a mapping ID, the workflow calls Stedi Mappings to translate the input JSON into something [EDI Translate](https://www.stedi.com/docs/edi-translate) can understand. Otherwise, it assumes the JSON is already prepared for EDI Translate.
7. It then passes the guide ID from the partnership information and the JSON to EDI Translate, which will translate it to X12 EDI.
8. The workflow will deliver the result to a destination configured in the partnership. The destination can either be a Stedi bucket or a webhook. The webhook can be any API endpoint; it doesn’t have to be related to Stedi.

If you’re curious how the bootstrap workflow works and how it uses the different Stedi products, this will give you a good overview.

Understanding the workflow

Understanding the bootstrap workflow


The easiest way to get started with Stedi is by using the [bootstrap repository](https://github.com/Stedi-Demos/bootstrap). It sets up a workflow for receiving and sending EDI documents, and you can adjust it to your needs.

- [Adjusting the Bootstrap workflow to your needs](/docs/bootstrap/adjusting-the-workflow). You’ve cloned and set up the Bootstrap workflow; now you’re ready to make it work for your use case.
- [Understanding the Bootstrap workflow](/docs/bootstrap/understanding-the-workflow). If you’re curious how the workflow works and how it uses the different Stedi products, this will give you a good overview.

The bootstrap repository let’s you get up and running quickly when starting with Stedi.