What your automation will do…
Refer to Foodpanda – How to create a connection.
Methods List and Settings Copy Link
Get Store Status Copy Link
note: A 204 response indicates that the system is processing your request. The result is not yet determined, and you must retry to obtain the final status.
See Foodpanda Get Available Status API reference.
Configuration Table:
Input Options:
- Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
- Default Value: You can specify a fixed attribute.
| Name* | Get Store Status |
| Connection* | Select your connection or create one. |
MATCHING CRITERIA
Chain Code*
This field uniquely identifies restaurant POS groups within the Middleware, preventing ID conflicts between different POS systems using the same chainVendorId. Its value is established during onboarding with Delivery Hero Ops team.
POS Vendor ID*
This field, also known as remoteId, uniquely identifies a restaurant for the POS plugin when paired with chainCode. The chainCode is a plugin-embedded value, configured during onboarding with Delivery Hero Ops team.
(*) required field
Response sample
[
{
"availabilityState": "UNKNOWN",
"availabilityStates": [
"CLOSED_UNTIL",
"CLOSED",
"OPEN"
],
"changeable": false,
"closedReason": "OTHER",
"closingMinutes": [
240,
720,
120,
60,
30
],
"closingReasons": [
"TOO_BUSY_KITCHEN",
"CLOSED",
"TOO_BUSY_NO_DRIVERS",
"TECHNICAL_PROBLEM",
"UPDATES_IN_MENU",
"OTHER"
],
"platformId": "12",
"platformKey": "TB",
"platformRestaurantId": "123456789",
"platformType": "TALABAT"
},
{
"availabilityState": "OPEN",
"availabilityStates": [
"CLOSED_UNTIL",
"OPEN"
],
"changeable": true,
"closingMinutes": [
120,
60,
30
],
"closingReasons": [
"OTHER"
],
"platformId": "36",
"platformKey": "FO_DE",
"platformRestaurantId": "kg6y",
"platformType": "FOODORA"
},
{
"availabilityState": "OPEN",
"availabilityStates": [
"CLOSED_UNTIL",
"CLOSED_TODAY",
"OPEN"
],
"changeable": true,
"closingMinutes": [
120,
60,
30
],
"closingReasons": [
"TOO_BUSY_KITCHEN",
"CLOSED",
"TOO_BUSY_NO_DRIVERS",
"TECHNICAL_PROBLEM",
"UPDATES_IN_MENU",
"OTHER"
],
"platformId": "1",
"platformKey": "LH_DE",
"platformRestaurantId": "40788",
"platformType": "DELIVERY_HERO"
}
]Update Store Status Copy Link
Note: It should first be checked which kind of availability changes are allowed by using Get Store Status and verifying that the
changeable property is true otherwise the request will be unsuccessful.See Foodpanda Update Availability Status API reference.
Configuration Table:
Input Options:
- Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
- Default Value: You can specify a fixed attribute.
| Name* | Update Store Status |
| Connection* | Select your connection or create one. |
MAP FIELDS [+ Add Field] ↓
Additional fields to configure the store status update.
Closed Reason
Specify the reason for closing, possible choices:
Closed – Update i n Menu – Holiday Special Day – Technical Problem – Refurbishment – Too Busy No Drivers – Bad Weather – Other.
Close Minutes
How long should a restaurant remains closed before opening again, e.g. 60. Works only with CLOSED_UNTIL availabilityState.
Chain Code*
This field uniquely identifies restaurant POS groups within the Middleware, preventing ID conflicts between different POS systems using the same chainVendorId. Its value is established during onboarding with Delivery Hero Ops team.
POS Vendor ID*
This field, also known as remoteId, uniquely identifies a restaurant for the POS plugin when paired with chainCode. The chainCode is a plugin-embedded value, configured during onboarding with Delivery Hero Ops team.
Availability State*
Possible states: Close – Close Until – Closed Today – Open
Platform Key*
Retrieve the Key from the Method Get Store Status. E.g. "platformKey": "TB".
Platform Restaurant ID*
Retrieve the ID from the Method Get Store Status. E.g. "platformRestaurantId": "123456789".
(*) required field
Response sample
[
{
"availabilityState": "UNKNOWN",
"availabilityStates": [
"CLOSED_UNTIL",
"CLOSED",
"OPEN"
],
"changeable": false,
"closedReason": "OTHER",
"closingMinutes": [
240,
720,
120,
60,
30
],
"closingReasons": [
"TOO_BUSY_KITCHEN",
"CLOSED",
"TOO_BUSY_NO_DRIVERS",
"TECHNICAL_PROBLEM",
"UPDATES_IN_MENU",
"OTHER"
],
"platformId": "12",
"platformKey": "TB",
"platformRestaurantId": "123456789",
"platformType": "TALABAT"
},
{
"availabilityState": "OPEN",
"availabilityStates": [
"CLOSED_UNTIL",
"OPEN"
],
"changeable": true,
"closingMinutes": [
120,
60,
30
],
"closingReasons": [
"OTHER"
],
"platformId": "36",
"platformKey": "FO_DE",
"platformRestaurantId": "kg6y",
"platformType": "FOODORA"
},
{
"availabilityState": "OPEN",
"availabilityStates": [
"CLOSED_UNTIL",
"CLOSED_TODAY",
"OPEN"
],
"changeable": true,
"closingMinutes": [
120,
60,
30
],
"closingReasons": [
"TOO_BUSY_KITCHEN",
"CLOSED",
"TOO_BUSY_NO_DRIVERS",
"TECHNICAL_PROBLEM",
"UPDATES_IN_MENU",
"OTHER"
],
"platformId": "1",
"platformKey": "LH_DE",
"platformRestaurantId": "40788",
"platformType": "DELIVERY_HERO"
}
]Test run or automate your Flow Copy Link
After setting up your Flow, you can choose to:
- “Run once”, your Flow will run only a single time. You can use this function to test your Flow. Refer to how to set up an HTTP Trigger, in the “Create a Flow” step.
- “Run Scheduler” will automate your Flows with the recurrence rule you previously defined.
For more details, refer to How to run a Flow tutorial in our Help Center.
If you are using a Webhook Trigger, the Flow will initiate automatically when a webhook is received from your connected apps. This means that the Flow is automated without a scheduler and will run until you deactivate the Flow manually. Refer to Webhook documentation in our Help Center.
If you need an integration that you cannot find in Wiresk, you can make a request to our team, and we will try our best to satisfy your needs.