tidyAgent user guide

1. Install

1. Install tidyAgent from the Webflow Marketplace.
2. Approve the Data Client permissions (see the permissions list on /install/webflow).
3. Complete onboarding in the hosted dashboard at agent.tidyflowapp.com.
4. Publish your Webflow site so the chat widget (Custom Code) is live for visitors.

Reopen anytime from the Webflow Marketplace app or agent.tidyflowapp.com/webflow.

2. Configuring the AI assistant

Go to AI Agent in the dashboard sidebar.

• Name, photo, greeting — how the bubble introduces itself on the live site.
• Colors & position — widget primary color, optional gradient, text colors, bottom-left or bottom-right.
• Personality & focus — friendly / professional / casual, and whether the agent prioritizes support, sales, leads, products, or bookings.
• Specialists (plan-dependent) — extra agents that only see the knowledge scopes you assign.
• Voice — spoken replies when your plan includes voice.

Use the live preview in Agent Studio before publishing style changes.

3. Managing business knowledge

Open Knowledge. tidyAgent builds answers from:

• Webflow Data APIs — site profile; page metadata (title, SEO description, published path) from GET /v2/sites/{site_id}/pages; CMS collections and items; ecommerce products when your plan and site include them. Static page body content via GET /v2/pages/{page_id}/dom is not used.
• Owner notes — prices, exceptions, or private instructions you type; these sit above API knowledge and are never overwritten by a rescan.

Click Read site via Webflow APIs (or re-run the scanner) after you publish major content changes. Domain crawling / scraping of the published site is not used for Webflow.

4. Setting up WhatsApp support

During onboarding (Your team) or later in Agent / settings for human support:

1. Enter the team member’s WhatsApp number with the correct country code.
2. Save. Visitors who choose WhatsApp open a handoff that continues the request on WhatsApp.
3. You can also capture email when WhatsApp is not chosen (lead form in the widget).

WhatsApp is optional. Without a number, visitors still get AI answers and can leave email for follow-up.

5. Managing conversations

Open Inbox (or Conversations) in the dashboard.

• See live and past visitor threads for this Webflow site only.
• Open a thread to read the full transcript and reply as a human when needed.
• Leads and WhatsApp handoffs appear in the same workspace so nothing is lost between channels.

6. Configuring human handoff

Handoff starts when the visitor asks for a person, or when the AI cannot answer confidently.

• Set the human team member name, role, email, photo, and optional WhatsApp in onboarding or Agent Studio.
• The widget shows a support choice (email / WhatsApp) instead of inventing an answer.
• Watch the Inbox for new handoffs and continue the conversation from there.

7. Updating support rules and behavior

• Owner notes (Knowledge) — highest priority rules, including private notes visitors never see.
• Agent focus & personality (AI Agent) — how the employee spends its time and tone.
• Specialist scopes — limit what each specialist can see (products, policies, etc.).
• Rescan after Webflow content changes so API knowledge stays current.

8. Chat widget (Custom Code)

On install / open, tidyAgent registers a compact inline loader through Webflow’s Custom Code API. That loader loads the production executable widget.js (the chat UI itself), then the script is applied at the site footer.

• Exact production URL — https://agent.tidyflowapp.com/widget.js (SemVer query v= plus site instance query for workspace binding).
• How it is registered — POST /v2/sites/{site_id}/registered_scripts/inline with sourceCode that loads widget.js, then PUT /v2/sites/{site_id}/custom_code to apply it at the footer.
• One production path — inline registration only. Hosted script registration is not used. There is no alternate Custom Code delivery path.
• What widget.js does — renders the chat UI and calls tidyAgent HTTPS JSON APIs for config and replies. It does not inject another remote script element.
• Where it runs — on your published Webflow site for visitors (after you publish).
• Why it is required — without it, visitors have no chat UI on the live site.

9. Uninstalling tidyAgent and removing its widget

Uninstalling from tidyAgent removes the Custom Code the App applied. Unrelated scripts are preserved. You must publish the Webflow site for the live bubble to disappear.

1. In tidyAgent Settings, click Uninstall & remove widget.
2. While your OAuth token is still valid, tidyAgent calls Webflow’s Custom Code API (DELETE /v2/sites/{site_id}/custom_code for App-applied scripts, with a safe fallback) and removes only tidyAgent’s applied widget. Other Custom Code is left alone. tidyAgent does not apply page-level scripts.
3. On the confirmation screen, publish your Webflow site so visitors stop loading the chat bubble. Publishing is required for the removal to take effect on the live site.
4. Optionally revoke the app under Webflow Site settings → Apps & integrations after Custom Code has been removed.

After uninstall we delete or anonymize associated workspace data after a reasonable retention period. You do not need to manually hunt for leftover tidyAgent snippets when uninstall runs successfully through Settings.

10. Troubleshoot

• No bubble on the live site — finish onboarding, confirm Custom Code applied, then Publish the site.
• Thin answers — re-run Knowledge via Webflow APIs; add owner notes for facts not in CMS/pages.
• Permission errors — reconnect from Webflow and approve the same Data Client scopes listed on the install guide.
• Billing — Webflow seats use card checkout in the tidyAgent billing page (not Wix/Shopify billing).