---
schema_version: "1"
id: d12f377cc624a544fc7e942d7c0f2efece9b61d3736b7d721ec38c6bebd099b8
title: Example Simple Custom HTTP Integration in Agentforce Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_integrations_custom_http_example.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_integrations_custom_http_example.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1088b94df4f3e03296ae19ae2a7188f6b8080dd5c0483d8f28dab64d1a76e7ef
description: Walk through an end-to-end example of creating a custom HTTP integration that looks up city and state information for a US postal code, and then adding it to a blueprint as an automation task.
products:
  - Cross Cloud
release: "264"
---
# Example Simple Custom HTTP Integration in Agentforce Operations

Walk through an end-to-end example of creating a custom HTTP integration that looks up city and state information for a US postal code, and then adding it to a blueprint as an automation task.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d19878e39">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d19878e39 ">
              <p>This feature is a workspace that’s external to your Salesforce org and requires
                an Agentforce Operations license. </p>
              <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
                executive.</p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d19878e73">Role or Access Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d19878e73 ">To manage integrations in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d19878e73 ">Admin role or Integration Admin role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d19878e73 ">To edit a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d19878e73 ">Admin role, Creator role, or a user with Edit access for the blueprint</td>

          </tr>
        </tbody>
      </table>

This example uses the at no additional cost Zippopotam.us API, which returns location information for a US postal code. Authentication isn't required. You create the integration and then add it to a blueprint so the lookup runs automatically when a workflow reaches that stage.

The integration sends a GET request to `https://api.zippopotam.us/us/90210` and extracts the city name and state abbreviation from the response.

#### See Also

- [Create a Custom HTTP Integration in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_integrations_custom_http_create.htm&release=264.0.0&type=5 "Create a Custom HTTP integration to connect Agentforce Operations to an external API. Use Custom HTTP integrations to send or retrieve data during workflow execution.")
- [Add a Custom HTTP Integration to a Blueprint in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_integrations_custom_http_blueprint.htm&release=264.0.0&type=5 "Add a custom HTTP automation task to a blueprint stage to automatically send or retrieve data when a workflow reaches that stage.")

## Create the Postal Code Lookup Integration

1. In the navigation sidebar, click **Admin**.
2. Click the **Integrations** tab.
3. Click **Add integration**.
4. For Integration Type, select **Custom HTTP**.
5. For Name, enter Postal Code Lookup.
6. For Type, select **None**. This API requires no authentication.
7. For Base URL, enter https://api.zippopotam.us.
8. For Method, select **GET**.
9. For Path, enter /us/90210.
10. Leave Headers, Query parameters, and Body fields blank.
11. For HTTP Response, configure the values to extract from the API response.
    1. Click **\+ Add value**. For the JSON Path expression, enter .places\[0\]\["place name"\]. Select the Agentforce Operations field to store the city name. For example, **City**.
    2. Click **\+ Add value**. For the JSON Path expression, enter .places\[0\]\["state abbreviation"\]. Select the Agentforce Operations field to store the state abbreviation. For example, **State Abbreviation**.
12. Click **Next**.
13. For Health check, select **Disabled**. The Zippopotam.us API doesn't provide a health endpoint.
14. Click **Create**.
    
    The integration configuration window closes.
15. In the integration list, find your new integration.
16. Click the three-dot dropdown list next to the integration and select **Edit**.
    
    The integration configuration panel opens.
17. Open the **Test HTTP request** section and click **Test**.
    
    The test results show the city (Beverly Hills) and state abbreviation (CA) extracted from the response. Confirm that the extracted values appear in the fields you selected.
18. Close the integration configuration window.

The Postal Code Lookup integration is complete available to use in blueprints.

## Add the Postal Code Lookup Integration to a Blueprint

1. [Create a blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_blueprint.htm&release=264.0.0&type=5 "Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.") or [edit an existing blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_edit.htm&release=264.0.0&type=5 "Open an existing blueprint for editing to add stages, tasks, automations, or other changes.").
2. In the blueprint, in the stage where you want the lookup to run, click **\+ Automation**.
3. Point to **Custom HTTP** and select **Postal Code Lookup**.
4. For Start, select **When the stage starts**.
5. Click **Add**.

The Postal Code Lookup automation task is added to the stage. When a workflow reaches this stage, Agentforce Operations automatically calls the postal code API and populates the city name and state abbreviation fields in the workflow.