7Loc
E-commerceConnect AI agents to 7Loc, an AI-powered hospitality platform for guest mobile ordering. Agents start guest carts and scan receipts into loyalty checks, and read the store catalog, shipping options, loyalty configuration, and coupon terms behind each venue.
What This Integration Enables
7Loc is a hospitality platform for guest mobile ordering, QR menus, loyalty and eWallet payments, and its Client API is guest facing by design. That single fact shapes everything about how you should build on this connector, so it is worth stating before the capabilities rather than after them. The reads are broad and genuinely useful. Get Account resolves the group that owns your token along with its brands, stores, bots and settings, which is the entry point every other operation depends on. Stores are addressable by identifier, by proximity to coordinates through Find Nearest Store, by a guest's address through Find Store By Location, and by city, each carrying working hours, contacts, supported fulfilment types and payment configuration. The catalogue is a full read surface with cursor paging, search, category filtering and sorting, plus Get Category Tree for the nested menu, Find Product Modification for resolving a variant from selected characteristics, and Get Price Range for building filters. Shipping is priced properly rather than estimated, since Get Shipment Price calculates delivery for a store given an order total and destination and reports the threshold for a cheaper tier where one exists. Loyalty configuration, coupon terms, invitation details and the loyalty card preview are all readable, as are the custom web pages and in store QR menus the guest app renders.
What this connector does not do is equally important. Guest account operations, meaning personal cards, order history and wallet, require an end user session token issued when a guest signs in, and this integration does not hold one and does not expose them. So an agent here can browse a catalogue, price a delivery, quote a coupon's terms and assemble a cart, and it cannot place an order on a guest's behalf, take a payment, cancel anything, or read a specific guest's balance. Two operations write, and only two. Create Cart creates a guest cart for a store, optionally pre filled with products, and returns the cart with its identifier and computed totals for a person or the guest app to carry forward. Scan Receipt submits a scanned receipt payload for processing, optionally linked to an existing order and store, and can create a loyalty check from it. Configuration is a single group API token sent as the X-Auth-Token header, which identifies and scopes the account rather than a person. There are no triggers, so nothing on 7Loc starts a flow: work here begins from a schedule or from an event in another system, and a cart or a receipt is checked by re reading it. Agents do the browsing, the pricing and the assembling. The call that puts value on a guest's loyalty account is where human-in-the-loop oversight belongs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A concierge request answered from the live menu of the right venue
A hotel guest asks for a delivery order and the answer needs to be correct about three things: which venue serves them, what that venue is actually selling tonight, and what delivery costs. The agent calls Get Account first to resolve the group, brand and store identifiers, then Find Store By Location with the guest's address, or Find Nearest Store with coordinates, which is a different question from listing every branch. With the store settled it reads the menu properly: List Categories or Get Category Tree for the structure, List Products with search and category filters for what is available with prices, images and modifiers, and Find Product Modification where the guest has picked characteristics such as a size or a preparation, so the variant and its price are resolved rather than assumed. Get Shipment Price then calculates delivery for that store against the order total and destination, and reports the threshold for a cheaper tier where one exists, which is the single most useful thing to tell a guest before they decide. Create Cart assembles the result and returns the cart identifier and totals, and the guest completes the order in 7Loc rather than the agent completing it for them.
Loyalty terms quoted accurately, every time
Loyalty programmes are usually explained from memory, which is how a guest ends up believing something the terms do not say. The reads here fix that without automating anything sensitive. Get Loyalty Settings returns the programme configuration resolved from the current context, covering bonus, coupon and referral behaviour, and Get Brand Loyalty Settings does the same for a specific brand and optionally a store. Get Coupon Info returns a coupon's title, discount terms, validity window and redemption status, so a guest asking whether their code still works gets a fact rather than a guess. Get Invitation Info resolves a referral code to the inviting party and the reward on acceptance. Get Loyalty Card Preview returns the stamp or reward card template with its design and mechanics, which is what a front desk actually needs to explain how many stamps are left. The agent posts a plain language summary of the applicable terms to the venue channel in Slack when a query comes in, and the terms it quotes came from the platform rather than from a briefing document.
The guest app's own content kept honest
A brand's ordering app shows more than a menu. List Web Pages returns the custom client pages, informational and marketing content, optionally scoped to a store or filtered by type, and Get Web Page By Slug returns one with its title and rendered body. Get Page returns a built in platform page by name with its localised content. Get In-Store Menu returns a published QR menu by identifier with the categories and products configured for on premise ordering, which is frequently a different set from delivery. On a schedule, the agent reads the published pages and menus and compares them against what the brand's content source holds, flagging drift: an allergen note that changed in the master document but not in the app, an in store menu still listing a product the catalogue no longer returns, a page referencing opening hours that no longer match Get Store. It writes nothing. It produces a short list of differences into a base in Airtable and a message to the brand manager, which is what a read only surface is genuinely good for.
Human-in-Loop Highlight
Scan Receipt with Make Check enabled is the operation to gate here, and it is the more interesting of this connector's two writes precisely because it looks like a read. The call submits a scanned payload, a QR or barcode from a paper receipt, and returns the parsed receipt along with any loyalty result. With Make Check switched on it does something else as well: it creates a loyalty check from that scan, which is the mechanism by which a guest's purchase becomes bonus value on their loyalty account. Now consider what this connector holds and what it does not. It holds a group API token that scopes catalogue, store, shipping and loyalty reads. It does not hold an end user session token, so guest account operations, meaning personal cards, orders and wallet, are not available to it at all. That asymmetry is the whole argument. An agent can create loyalty value from a scanned receipt and has no operation anywhere in this surface that inspects, adjusts or reverses what it created. A double scanned receipt credits twice. A misread total from a smudged barcode credits the wrong amount. A batch of receipts processed against the wrong store attributes value to a venue that never made the sale, which distorts both the guest's balance and the branch's numbers. Every one of those is fixed by a human inside 7Loc, because nothing in the connector can undo it. So the flow is built the other way round. The agent scans and parses with Make Check off, which returns the parsed receipt without creating anything, checks the total and the store against what it expected, and posts to the venue host in Slack: "Receipt scan for guest booking 4417, Riverside branch. Parsed total 360 UAH, recognised true, store matched to Riverside from the scan payload. This guest has 2 receipts scanned in the last hour, one for 360 UAH at 19:12, which may be the same receipt. Creating a loyalty check credits bonus value and nothing in this connector can reverse it, since guest account operations need an end user session. Credit this receipt, skip it as a duplicate, or send it to the loyalty team?" A person answers once, and only then does the agent repeat the call with Make Check enabled. Create Cart sits behind a lighter version of the same reasoning: an agent may assemble a cart freely, because a cart is a proposal, but the cart identifier is handed to the guest or the host to complete rather than pushed onward, since there is no operation here that could cancel an order once it exists. This is the digital andon cord placed on the one call in a read heavy connector that creates value somebody else has to take away by hand.
Agent Capabilities
32 actionsAccount
4- Get Account Resolves the 7Loc group, meaning the business account, that owns the configured API token, returning the group with its brands, stores, bots and settings. This is the entry point for a flow, because the identifiers it returns are what every other operation is addressed by.
- Get Group Returns a group by its numeric identifier, including its display name, brands and general configuration.
- Get Group Auth Settings Returns the authentication settings for a group, describing which guest sign in methods, covering phone, email and Telegram, are enabled for its ordering apps.
- Get Group Appearance Settings Returns the appearance settings for a group, including theme colours, logo and branding applied across its guest facing ordering interfaces.
Stores
6- List Stores Lists the stores belonging to the account's brand, optionally filtered by fulfilment capability and city, each with its address, working hours and supported fulfilment types.
- Get Store Returns a single store by identifier, including address, contacts, working hours, supported fulfilment types and payment configuration.
- Find Nearest Store Finds the store closest to a set of coordinates and returns it with its distance from the supplied point.
- Find Store By Location Finds the store serving a given location, resolved from coordinates or a free text address. This is the operation that decides which venue fulfils a guest's delivery address.
- List Cities Lists the cities in which the account's brand has stores, optionally filtered by the fulfilment type available in each.
- Get Brand Returns a brand by identifier. A brand groups stores under a shared catalogue, appearance and loyalty configuration.
Catalog
7- List Products Lists the products in a store's menu with cursor based paging, full text search, category filtering and sorting, returning prices, availability, images and modifiers.
- Get Product Returns a single product from a store's catalogue with its description, price, images, characteristics, modifiers and stock status.
- Get Price Range Returns the minimum and maximum product prices for a store's catalogue, which is what a price filter is built from.
- Find Product Modification Resolves a specific product variant from a set of selected characteristic values or filters, returning the matching modification with its price and availability. Use it rather than assuming a variant's price from the parent product.
- List Categories Lists a store's menu categories as a flat list, optionally scoped to the children of a parent category or filtered by a product search term.
- Get Category Tree Returns a store's categories as a nested tree, preserving parent and child relationships for rendering a hierarchical menu.
- List Store Filters Returns the configured product filter sets, meaning characteristics and their possible values, for a store.
Shipping
3- List Shipments Lists the delivery methods available for a store, such as courier delivery, pickup or self service, each with its base configuration.
- List Custom Shipments Lists the custom shipment methods configured for the account's brand beyond the built in delivery types.
- Get Shipment Price Calculates the delivery price for a store given an order total and destination, returning the applicable price and, where relevant, the threshold for a cheaper tier. Quote this before a guest decides rather than after.
Loyalty
5- Get Loyalty Settings Returns the loyalty programme settings for the account's brand as resolved from the current context, including bonus, coupon and referral configuration.
- Get Brand Loyalty Settings Returns the loyalty settings for a specific brand, optionally scoped to a store or an invoice template.
- Get Coupon Info Returns public information about a loyalty coupon for a brand, including its title, discount terms, validity window and redemption status.
- Get Invitation Info Returns information about a referral or loyalty invitation for a brand identified by its invitation code, including the inviting party and the reward on acceptance.
- List Special Accounts Lists the special loyalty accounts available in the current context, such as bonus, gift card or corporate wallets, filtered by audience scope.
Ordering
2- Create Cart Creates a guest cart for a store, optionally pre filled with products, and returns the cart with its identifier and computed totals. The cart is a proposal that a guest or a host completes in 7Loc, since no operation here places or cancels an order.
- Scan Receipt Submits scanned receipt data, such as a QR or barcode payload, for processing, optionally linked to an existing order and store, and returns the parsed receipt and any loyalty result. With Make Check enabled it creates a loyalty check, which credits value that nothing in this connector can reverse.
Content
5- List Web Pages Lists the account's custom client web pages, the informational and marketing content shown in the guest ordering app, optionally scoped to a store or filtered by page type.
- Get Web Page By Slug Returns a single custom client web page by its slug, including its title and rendered content body.
- Get Page Returns a built in platform page by name, such as a system informational page, with its localised content.
- Get In-Store Menu Returns a published in store menu by identifier, including the categories and products configured for on premise QR ordering, which is often a different set from the delivery catalogue.
- Get Loyalty Card Preview Returns the public preview of a loyalty stamp or reward card template, including its design and the stamp or reward mechanics it defines.
Frequently Asked Questions
What can FlowRunner do with 7Loc?
FlowRunner agents can run Get Account, Get Group, and Get Group Auth Settings in 7Loc, plus 29 more actions.
Does connecting 7Loc to FlowRunner require OAuth?
No. 7Loc connects to FlowRunner with an API key, no OAuth flow required.
Can 7Loc trigger a FlowRunner workflow automatically?
7Loc doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with 7Loc
$100 in credits. No card required. Connect in minutes.