No content to show
User Activity
3 hours ago
Yes, you can call the API directly using Send HTTP request to retrieve the field. Example request for another field:
{
"query": "query ProductCollection($collectionID:ID!, $productID: ID!) { product(id: $productID) { id\n inCollection(id: $collection...
If you can create a test order that uses Facebook or Instagram, you can use the sample data feature in Flow to see where, if anywhere, "Facebook" or "Instragram" are stored. Docs https://help.shopify.com/en/manual/shopify-flow/create/preview-data#sam...
I can't give an exact date because it's still in progress and we might discover more issues. Ideally, it's very soon.
It's not quite clear what you are asking. The inventory trigger is not aware of where the inventory came from, but just that it changed. And I'm not aware of any Purchase Order / Inventory specific functionality in Shopify.
06-10-2025
You could just store the data in a metafield and then once a week send that data out.
Something like:
Order createdUpdate shop metafield (increment the number stored)
In a second workflow
Every weekSend email (with shop metafield data)Update sho...
Not possible to override it currently. You can instead use Send Admin API request to call the API directly. In that action you can specify your own order id
You need to modify anywhere there is a reference to a metafield, colors, and tags. That's quite a few places, so if you want to go that route then try changing it and ask questions where you get blocked.
It would replace all of these blocks with a single Run code and a single "update product variant metafield". You could continue with using a bunch of conditions and actions like this, but it may get unmanageable as you add more and more of them.
There is multiple threads here talking about how to convert tags to metafields and one about colors. The same approach applies here, you just need to use the title instead of tags. There's also a template that will get you most of the way there: http...
I looked at the code for this and it only handles plurals:
seconds, minutes, hours, days, weeks, months, years
I think the date_minus filter is not handling the singular of "days" well. Try "1 days" or "24 hours"
None of these are real actions. Please don't post AI-generated responses here without double-checking they are accurate.
06-05-2025
I think I found the workflow through a support ticket. You have at least 2 issues. First, you are using a metafield that is assigned to product categories and not a product. I'm not sure how these work exactly...are you sure you want to be setting a ...
We do store info in cookies, but it's not guarantee that it will generate an abandonment as what happens depends on browser settings and user behavior.
One thing...I think you need quotes around that date so:created_at:>"{{ scheduledAt | date_minus:"one day"}}"
If that doesn't work DM me a link to the workflow so I can check it out in more detail
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 321 | 06-11-2025 09:05 AM | |
| 694 | 06-04-2025 12:11 PM | |
| 551 | 06-04-2025 12:08 PM | |
| 622 | 05-28-2025 03:54 PM | |
| 529 | 05-19-2025 02:24 PM |
