> For the complete documentation index, see [llms.txt](https://limechatai.gitbook.io/limechat-product-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limechatai.gitbook.io/limechat-product-guide/whatsapp-marketing/flows/action-nodes/fetch-address.md).

# Fetch Address

Action Node · Shopify Customer Address Retrieval

### What It Does

This node fetches the customer’s saved address from Shopify using the phone number associated with the current WhatsApp conversation.

It helps auto-fill delivery details during checkout or order placement workflows, reducing the need for customers to manually enter address information.

This improves checkout speed and creates a smoother conversational commerce experience.

***

### Example

A customer confirms they want to place an order through WhatsApp.

Instead of asking the customer to manually type their shipping address, the workflow automatically fetches the saved Shopify address linked to their phone number.

The workflow can then:

* Show the saved address for confirmation
* Proceed directly to checkout
* Use the address for shipping calculations

***

## When to Use This Node

Use this node when:

1. You need the customer’s saved delivery address before creating an order
2. You want to reduce friction during checkout
3. You are building conversational commerce or WhatsApp ordering flows
4. You want to auto-fill customer information instead of collecting it manually
5. You need address information before payment or shipping workflows

***

## Requirements

Before configuring this node:

* Shopify must already be connected to your LimeChat account
* The customer phone number should exist in the ongoing conversation
* The customer must already exist in Shopify with a saved address

***

## Supported Events

This node supports:

1. All Events

***

## Setting It Up

### Inputs

| Input            | Type     | Required | Description                                                                      |
| ---------------- | -------- | -------- | -------------------------------------------------------------------------------- |
| Ecom Integration | Dropdown | Yes      | Select the e-commerce platform from which the customer address should be fetched |

***

## Input Field Details

### Ecom Integration

Choose the e-commerce platform connected to the workflow.

Currently supported:

* Shopify

#### Special Behavior

* Uses predefined selectable options
* Currently limited to Shopify integration support

***

## Special Behavior

* The node automatically uses the customer’s phone number from the active conversation
* Searches Shopify for a matching customer record
* Retrieves the customer’s saved address if available
* No manual customer lookup is required

***

## Outputs

| Output     | Type          | Description                                            |
| ---------- | ------------- | ------------------------------------------------------ |
| address    | Text / Object | Customer’s saved address retrieved from Shopify        |
| successful | Boolean       | Indicates whether the address was successfully fetched |

***

## Output Behavior

| Output Value       | Meaning                        | Recommended Next Step                    |
| ------------------ | ------------------------------ | ---------------------------------------- |
| successful = true  | Address fetched successfully   | Proceed with checkout or order creation  |
| successful = false | Address could not be retrieved | Ask customer to manually provide address |

***

## What Happens After It Runs

Once executed:

* The workflow checks Shopify for a customer matching the current phone number
* Saved address information is retrieved if available
* The address becomes available for downstream workflow steps such as:
  * Order creation
  * Shipping calculations
  * Checkout confirmation
  * Payment flows

***

## Best Practices

 Use this node before:

* Order creation
* Shipping estimation
* Payment collection
* Checkout confirmation

 Always include a fallback flow if no address is found.

 Allow customers to confirm or update fetched addresses before placing the order.

 Combine with:

* Order creation workflows
* Payment link generation
* COD verification
* Conversational checkout flows

 Ensure customer phone numbers are stored consistently in Shopify for accurate matching.

***

## Key Reminders

1. Shopify integration is mandatory
2. The node relies on the customer’s phone number from the ongoing conversation
3. Works across all workflow events
4. If no Shopify customer or address exists, the fetch may fail
5. Typically used before order placement or payment workflows
6. Helps reduce checkout friction in conversational commerce journeys
7. Currently supports Shopify only