> For the complete documentation index, see [llms.txt](https://lrvdlinden.gitbook.io/myparcel-for-homey/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lrvdlinden.gitbook.io/myparcel-for-homey/en/examples.md). # Flow examples A few useful Flows to get started. Card titles are as in Homey; the full list is on [Flow cards](/myparcel-for-homey/en/flows.md). ## 1. Notify with the parcel image when PostNL is coming * **When:** *A parcel status changed* (PostNL) * **And:** *The current parcel status is* `Courier is on the way` * **Then:** Send a push notification with image: text `[[Package sender]] arrives between [[Delivery window]]`, image the card's **My delivery image** token. The image is pinned to exactly this parcel and status. To use the image in another Flow (e.g. a time trigger), pick the global token **\ · Parcel image**. ## 2. Out for delivery (other carriers) * **When:** *DPD parcel out for delivery* (or the *out for delivery* card of DHL, GLS, Trunkrs, Dynalogic, Dragonfly, Amazon …) * **Then:** Send a notification `[[Sender]] arrives today, [[Delivery window]]`. ## 3. Pickup code for Vinted Go or InPost * **When:** *Vinted Go parcel ready for pickup* * **Then:** Send a notification `Pick up at [[Pickup point]] with code [[Pickup code]]`. ## 4. New mail with scan * **When:** *New mail is expected* (PostNL) * **Then:** Send a notification with the card's **Mail item image** token, or use **\ · Latest mail scan** in any other Flow. ## 5. Track a tracking number automatically * **When:** e.g. an e-mail or webhook Flow that carries the tracking number * **Then:** *Track Trunkrs parcel…* (or *Track GLS parcel…*, *Track DHL parcel…* …) with the number as argument. Clean up later with *Remove delivered … parcels*. ## 6. Nobody home? * **When:** Everybody left * **And:** *A … parcel is out for delivery* * **Then:** Send a reminder to ask the neighbours or choose a pickup point. ## Advanced Flow tips * **One trigger card per action chain.** Tokens only exist in the Flow started by *that* card. If you connect two triggers to the same action block that uses a token of one of them, Homey reports *Missing token value* as soon as the other trigger fires. * **Or use global tokens.** The global PostNL tokens (**Parcel image**, **Latest mail scan**, status, delivery window …) and the MyParcel delivery tokens work in every Flow, whichever card started it. See [Flow tokens](/myparcel-for-homey/en/tokens.md). * Cards fire once per change – also after a restart. You don't need to filter duplicate notifications yourself. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://lrvdlinden.gitbook.io/myparcel-for-homey/en/examples.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.