Update Address in Recharge When Shopify Customer is Updated

This scheduled trigger runs once per day at midnight. The timing provides complete coverage of the previous day's customer updates and processes them before subscription charges run.

Customization: You can adjust the schedule to run more frequently if address synchronization needs to be more immediate, or less frequently if you prefer batch processing.

This step fetches Shopify customers using time-based filtering. The query includes updated_at_min set to 24 hours ago (calculated using date math that subtracts 1 day from current time) and limit of 250 customers. This returns customers who updated any information in the past day, which may include address changes, email updates, or other profile modifications. The 250 limit is Shopify's maximum per request—if you have more than 250 updates daily, you'd need pagination logic.

What triggers "updated": Shopify updates the updated_at timestamp when customers modify their profile, when admins edit customer records, when apps update customer data, or when orders associate with customers for the first time.

This filter checks if the customer array is not empty. If true (customers exist), the workflow proceeds. If false (no customers updated), the workflow stops here. This is especially useful for days with low customer activity where running the full workflow would be wasteful.

This loop iterates through each customer in the array from step 2. For every customer, the loop executes the subsequent Recharge lookup, address retrieval, comparison, and update steps. This per-customer processing ensures one customer's sync failure doesn't prevent other customers from updating.

This filter checks if the customer's email field does not equal "null". If true (email exists), the workflow proceeds to Recharge lookup. If false (no email), this customer is skipped. Some customers created through certain channels or bulk imports might lack email addresses.

This step queries Recharge's customer database using the email address as the search parameter. It returns matching Recharge customer records with the Recharge customer ID needed for address retrieval. The first result (index 0) contains the customer's Recharge data including customer ID, subscription status, and account details.

Email matching: Recharge uses email as the primary identifier for customer lookups. Customers must use the same email in both Shopify and Recharge for this workflow to link accounts correctly.

This filter checks if the Recharge customer array is not empty. If true (Recharge account exists), the workflow proceeds. If false (no Recharge account), this customer is skipped. Many Shopify customers don't have subscriptions, so this filtering is essential to focus only on actual subscription customers.

This step queries Recharge for addresses belonging to the Recharge customer ID. It returns address records including address1, address2, city, province, zip, country_code, phone, and name fields. The first address (index 0) is used for comparison—this is typically the customer's primary subscription shipping address.

Multiple addresses: Customers can have multiple addresses in Recharge (different subscription shipping addresses). This workflow updates only the first address. To sync all addresses, you'd need additional loop logic.

This filter implements comprehensive address comparison using OR logic. The workflow proceeds if ANY of these fields differ between Recharge and Shopify:

1. address1: Primary address line (street address, P.O. box)
2. address2: Secondary address line (apartment, suite, unit)
3. city: City name
4. province: State/province
5. zip: Postal code
6. country_code: Country code (like US, CA, GB)

OR logic reasoning: If even one field differs, the address needs updating. The OR operator ensures any discrepancy triggers synchronization, not just complete address mismatches.

This step updates the Recharge address using the Recharge address ID. The update includes:

1. address1: Primary address line from Shopify default address
2. address2: Secondary address line from Shopify default address
3. city: City from Shopify default address
4. country: Country code from Shopify default address
5. customer_id: Shopify customer ID
6. first_name: Customer's first name
7. last_name: Customer's last name
8. phone: Customer's phone from default address (or "No phone number provided" if missing)
9. zip: Postal code from Shopify default address
10. province: State/province from Shopify default address

Phone number handling: The workflow includes conditional logic that provides a fallback message if no phone number exists, preventing Recharge API errors from missing required phone fields.

The update ensures Recharge has complete, current address information for accurate subscription fulfillment.