Wstores-Adloggs Automation via Pabbly Connect

@shayankhan333

The trickiest part of this setup isn't the webhook trigger, it's parsing Wstores' address payload into the exact format Borzo's API expects for pickup and drop coordinates. I've handled similar Pabbly flows where address fields come concatenated, and a simple formatter step between the webhook and the API call saves a lot of failed delivery requests. I'll set up the Pabbly workflow with the Wstores webhook trigger, build an address parser/formatter step, and configure the Borzo API call with your Pune store as the fixed pickup point. One thing to watch: Borzo's API has specific rate limits on delivery creation that need a retry step if you're batching orders. 1) Does Wstores send a structured address (city, pin, street separately) or one merged field? Happy to talk details in chat. Shayan

@EhsanWebCreator

I can connect Wstores to Adloggs/Borzo through Pabbly using a webhook trigger, validate and normalize the order and address payload, then call the rider pickup endpoint with clear error handling and retry logic. I will test both successful and failed orders and document the field mapping. Please share the API documentation and sample payloads before kickoff.

@farukhkaleem1

Harnessing the power of PHP, I can expertly command Pabbly Connect to establish a seamless automation workflow between your Wstores and Adloggs/Borzo API. My depth in web development is showcased in my strong grasp on HTML, CSS, JavaScript and jQuery. Additionally, my proficiency extends to more complex languages like PYTHON, C++ which gives me an edge while navigating algorithm building challenges that come with hooking up APIs such as this. Moreover, my strong adaptability and quick learning make me well-suited for your project,. Currently, I'm growing my skills in Laravel and React.js- powerful frameworks that enhance web development capabilities. From a time perspective, I know how crucial speed is in the digital world; it's a key parameter I used to land your project -quick kick-offs and punctual delivery. Partnering with me means not just hiring an automation expert but also getting a committed ally towards your digital vision. Let's transform your concept into a functional reality with precision and efficiency, ensuring the automation will run smoothly while exceeding your expectations. Can't wait to embark on this immensely productive journey together.

@nikitau26

I work with Pabbly Connect regularly for exactly this kind of webhook-to-API bridge. The flow is straightforward on paper: Wstores webhook fires on new order, a formatter step parses/cleans the customer address, then a router calls the Adloggs/Borzo pickup request API with your Pune store as origin and the parsed address as destination. A few things I'd confirm before locking scope: does Wstores support outbound webhooks natively (some order platforms only expose polling APIs, which changes the trigger setup), and do you already have API credentials/docs for Adloggs or Borzo (whichever one is the actual delivery partner, the description mentions both)? If addresses come through as free text rather than structured fields, I'd add a light parsing step (regex or a geocoding lookup) so the pickup request doesn't fail on messy input. Happy to start as soon as I can see the webhook payload sample and the delivery API docs.

@VowDev

Your order flow needs to go: Wstores order placed → webhook fires → Pabbly parses the payload (customer name, address, phone, items) → Borzo/Adloggs API creates a delivery request with your Pune store (411047) as pickup. I can set this up end to end. What I'll deliver: - Pabbly workflow: webhook trigger catching Wstores order events, data formatter to extract and map address fields, HTTP module calling Borzo's Create Order endpoint with your store as pickup point - Address parsing logic to handle the variations Indian addresses come in (flat/floor/landmark/pincode) - Error handling so you get notified if a delivery request fails instead of losing the order - Documentation of the full flow so you can maintain it I've built similar webhook-to-API pipelines before — the pattern is the same whether it's Pabbly, Make, or raw code. The key is getting the address mapping right and handling edge cases (missing pincode, incomplete address). One question: does Wstores send a webhook on order creation by default, or do you need that configured first? Knowing this helps me scope Day 1 accurately.