WEBLUCY
Web PlatformManage contacts, members, store, and marketing data on a WEBLUCY website, covering contacts, members, products, and orders. Agents keep site data aligned with the systems of record behind it.
What This Integration Enables
WEBLUCY is the website, the store and the login-gated customer area behind one API key scoped to one domain. That single scope is convenient and it is also the reason to be precise, because the platform draws a distinction that automations get wrong constantly. Contacts are visitors identified by email, with tags, custom properties and subscriber list memberships. Members have credentials and group memberships that gate access to protected pages, courses and downloads. They are separate records, and the difference between deleting a contact and deleting a member is the difference between removing a marketing record and destroying somebody's login to something they paid for.
With that distinction held, this connector covers the whole site. Contacts create, update, search by exact email and delete, with Create Or Update Contact matching on email so a repeated sync never duplicates a person. Members create with optional group assignment and address, update, delete, and get a single sign-on URL through Start Member Session that lands them directly in the customer area for fifteen minutes. Member groups list, create and delete, which is where paid access actually lives. The store covers products with options, variants and subscription configuration, product categories, and orders with totals, taxes, discounts, line items, addresses, payment state and private notes. Form submissions, bookings, subscriber lists, traffic and usage stats and a webhook audit round it out. A single trigger registers a site webhook on enable and removes it on disable, delivering the full order, product, contact, booking or form submission payload. Two behaviours are worth committing to memory: Create Product can update by URL instead of duplicating, and moving an order to Completed emails digital and membership buyers their access.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Access that follows the purchase without a manual step
An order for a membership product completes. On Website Event fires with the full order payload. The agent calls Search Member By Email, and where no account exists it calls Create Member with the buyer's details, omitting the password so WEBLUCY generates one and emails a reset link. It then assigns the group that unlocks the purchased content, resolved with List Member Groups. Where an account already exists, the agent updates the group list instead of creating a duplicate. The buyer gets in on their own, in minutes, without anyone opening the admin.
One contact record across the site and the marketing stack
A form submission arrives. The agent calls Create Or Update Contact, which matches on email and writes only the fields supplied, then attaches the person to the right subscriber list resolved with List Subscriber Lists. The same record is pushed to Mailchimp so the audience there and the audience on the site are the same people. Because the create action is idempotent on email, the flow can run on a schedule as a safety net alongside the live trigger without producing duplicates.
A storefront catalogue that is not maintained twice
Prices and stock change in the system that owns them. The agent calls List Products and List Product Categories to resolve identifiers, reads the current definition with Get Product so it modifies rather than overwrites, and applies changes with Update Product. For new lines it calls Create Product with update-by-URL enabled, which makes a full catalogue sync idempotent rather than duplicative. Orders flow the other way into fulfilment and accounting through List Orders and Get Order, with Update Order recording fulfilment state as it moves.
Human-in-Loop Highlight
The question that needs a person on this connector is not whether to revoke access. It is which of the two doors to use, because WEBLUCY offers both and they are not equivalent. Update Member can change the group list or the approval state, and every part of that is reversible: put the group back and the person is in again. Delete Member permanently removes the member and their login, and the platform's own guidance is to unapprove with Update Member instead when the block should be reversible. Point an agent at a billing feed and the trap is obvious in hindsight. A failed charge is very often a card that expired, and it recovers on the retry. An automation that reads the first failure and reaches for the permanent door has deleted a paying customer's account over a card they were going to replace on Tuesday.
So the FlowRunner agent does the reconciliation and hands over the choice. It resolves each affected person with Search Member By Email, reads their group memberships and approval state with Get Member, and treats the batch as a human-in-the-loop decision, messaging the site owner: "Three members are flagged by today's billing sync. Dana Whitfield, second failed charge, has been a member fourteen months. Owen Cassidy, subscription cancelled by the customer in the portal. Priya Nandakumar, first failed charge on a card expiring this month. Unapprove all three, unapprove Owen only, or hold?" A person answers, and the agent applies exactly that, using Update Member unless a permanent removal was explicitly chosen.
One related habit belongs on the same page. Start Member Session returns a URL that logs whoever holds it straight into the customer area for the next fifteen minutes. That URL is a credential, not a link, so an agent generates it at the moment it sends it and sends it only to the member it belongs to, never into a shared channel or a ticket body.
Agent Capabilities
33 actionsContacts
6- List Contacts Returns a paginated list of every visitor identified by email on the website, optionally limited to a creation window. Page size runs from 1 to 50 with a default of 30, and the response carries items, total count, limit and skip so a whole audience can be paged.
- Create Or Update Contact Creates a contact, or updates the existing one when the email already exists, so repeated syncs never duplicate a person. Only the fields supplied are written, which makes partial updates from another system safe.
- Search Contact By Email Looks a contact up by exact email address. Used to check whether someone exists before creating them, or to resolve an email into the contact ID other actions need.
- Get Contact Retrieves a single contact by numeric ID, including tags, custom properties and subscriber list memberships. Used when a webhook or list step supplied an ID and the flow needs the full record.
- Update Contact Updates an existing contact by ID, writing only the fields supplied. Preferred over the create action when the contact ID is already known and email should not act as the match key.
- Delete Contact Permanently removes a contact from the website. Used for erasure requests and cleanup. The contact's orders and form submissions are separate records and are not affected.
Members
10- List Members Returns a paginated list of registered members, the people who can log into the customer area. Members are distinct from contacts: every member has credentials and group memberships that gate access to protected content.
- Create Member Creates a registered member with optional group assignments and addresses. Omitting the password has WEBLUCY generate one and email the member a reset link, which is the right behaviour when provisioning access after a purchase made elsewhere.
- Search Member By Email Looks a registered member up by exact email address. Used to check whether an account already exists before provisioning one, or to resolve an email into the member ID other actions need.
- Get Member Retrieves a single member by ID, including approval state, group memberships and stored addresses. Used to confirm entitlements before granting or revoking access.
- Update Member Updates a member's profile, group memberships or approval state. Changing the group list is how paid access is granted or revoked when a subscription starts or lapses elsewhere, and it is the reversible option when a block should be undoable.
- Delete Member Permanently removes a registered member and their login. Use Update Member to unapprove instead whenever the block should be reversible, which on a billing signal is almost always.
- Start Member Session Issues a single sign-on access URL that logs a member straight into the customer area, optionally landing on a specific page. The URL is valid for 15 minutes and functions as a credential, so generate it at the moment it is sent and send it only to the member.
- List Member Groups Returns the member groups defined on the site. Groups gate protected pages and courses, so this is the lookup step before assigning access on a member record.
- Create Member Group Creates a member group, optionally with a landing link members of that group are sent to. Used to stand up a new access tier without opening the admin.
- Delete Member Group Deletes a member group. Members previously in it lose the access it granted, so check membership with List Members before removing a tier.
Store
6- List Products Returns a paginated list of store products, optionally filtered by category or by a fragment of the title. Filtering by category includes everything in its subcategories.
- List Product Categories Returns the store's product categories. Used to resolve a category name into the ID the product filter expects, or to mirror the catalogue structure elsewhere.
- Create Product Creates a store product of a physical, digital, service or membership type, with images, categories, options and variants. Turning on update-by-URL has an existing product with the same URL updated instead, which is what makes a catalogue sync idempotent.
- Get Product Retrieves a single product with its full option, variant and subscription configuration. Read it before an update so a flow modifies the current definition rather than a stale copy.
- Update Product Updates an existing product by ID, changing title, description, visibility, imagery, options or variants. Used to push price and stock changes from the system that owns them into the storefront.
- Delete Product Removes a product from the catalogue. Existing orders referencing it keep their line items, so historical revenue reporting is unaffected.
Orders
3- List Orders Returns a paginated list of store orders, optionally limited to a creation window. Each order carries totals, taxes, discounts, line items and addresses, which makes this the feed to point at accounting or fulfilment.
- Get Order Retrieves a single order with its line items, taxes, discounts, shipping details, payment state and private notes. Read it before updating so a flow acts on the current fulfilment state.
- Update Order Updates an order's status, payment state, addresses or fulfilment details, writing only the non-empty fields supplied. Moving an order with digital downloads or membership products to Completed emails the customer their access, so set that status deliberately rather than as a bulk tidy-up.
Forms and Bookings
2- List Form Submissions Returns a paginated list of form submissions captured on the website, optionally limited to a time window. Used to sweep leads into a CRM on a schedule when a live trigger is not wanted, or as a safety net alongside one.
- List Bookings Returns a paginated list of booked sessions on the website or funnel, optionally limited to a time window or a single event. Used to mirror appointments into a calendar or to drive reminder messaging.
Subscriber Lists
4- List Subscriber Lists Returns the email marketing subscriber lists defined on the website. Used to resolve a list name into the ID that contact creation and updates expect.
- Create Subscriber List Creates an email marketing subscriber list. Contacts are then attached to it through the contact create and update actions.
- Update Subscriber List Renames an existing subscriber list. Membership is unaffected, so this is safe to run on a live list.
- Delete Subscriber List Deletes a subscriber list. The contacts themselves are kept and only their membership of this list disappears.
Analytics
1- Get Website Stats Returns website traffic or resource-usage statistics, with the shape of each row depending on the type requested. Hourly and daily give sessions and impressions over time, referrers, devices and browsers break traffic down by source, and usage reports current storage and bandwidth. Periods with no traffic are omitted rather than zero-filled, so a flow charting a series fills the gaps itself.
Webhooks
1- List Webhooks Returns the webhooks registered on the website with their target URLs, secrets and subscribed events. Used to audit which external systems are receiving live notifications from the site.
Triggers
1 triggersEvent Triggers
1- On Website Event Fires when the selected website events occur, delivering the full order, product, contact, booking or form submission payload rather than an identifier to look up. Used to provision access on a purchase, route a lead on submission, or mirror a booking into a calendar as it happens. A webhook is registered on the site when the trigger is enabled and removed again when it is disabled.
Frequently Asked Questions
What can FlowRunner do with WEBLUCY?
FlowRunner agents can run List Contacts, Create Or Update Contact, and Search Contact By Email in WEBLUCY, plus 30 more actions.
Does connecting WEBLUCY to FlowRunner require OAuth?
No. WEBLUCY connects to FlowRunner with an API key, no OAuth flow required.
Can WEBLUCY trigger a FlowRunner workflow automatically?
Yes. WEBLUCY supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with WEBLUCY
$100 in credits. No card required. Connect in minutes.