Flow Settings
Overview
The Flow Settings panel gives you full control over how your flow behaves, appears, and integrates with external tools. Settings are scoped per-flow, meaning each flow can have its own domain, metadata, collaborators, and integration credentials.
To access Flow Settings:
ZappWay Dashboard
└── Sidebar Menu → Tools → ZappFlux
└── Flow List → Select a Flow → Settings tab
├── General (name, icon, directory)
├── Metadata (title, description, OG image)
├── Custom Domains
├── Collaborators
└── Global Integrations
General Settings
The General tab controls the basic identity of your flow within the ZappWay dashboard.
| Setting | Description |
|---|
| Project Name | The internal display name used to identify the flow in the list view |
| Icon | The emoji or icon representing the flow in the dashboard |
| Directory / Folder | The folder this flow belongs to — use directories to organize flows by project, client, or team |
| Status | Published or Draft — controls whether the flow is live to end users |
| Flow URL | The public URL where the flow is accessible (read-only, based on your domain settings) |
Changing the Flow Name:
- Navigate to Settings → General
- Click the Project Name field
- Enter the new name
- Click Save
Renaming a flow does not change its public URL unless you are using the default ZappWay subdomain and have not yet set a custom domain. If a custom domain is configured, the URL is independent of the flow name.
Metadata controls how your flow appears in browser tabs, search results, and when its link is shared on social platforms and messaging apps.
| Field | Description |
|---|
| Page Title | The title shown in the browser tab and used by search engines |
| Description | The summary text shown below the title in link previews and search results |
| Favicon | The small icon shown in the browser tab — supports image upload (PNG, ICO, SVG) |
| OG Image (Share Image) | The featured image displayed when the flow link is shared on WhatsApp, Facebook, LinkedIn, Twitter/X, etc. |
| Custom HTML | Inject custom scripts or tags into the <head> or <body> of the flow page |
| Asset | Recommended Size | Format |
|---|
| Favicon | 32×32 px or 64×64 px | PNG, ICO, SVG |
| OG Image | 1200×630 px | PNG or JPG |
Always set an OG Image. When users share your flow link on WhatsApp or social media, a compelling preview image dramatically increases click-through rates compared to a blank or generic preview.
Custom HTML
The Custom HTML field allows you to inject third-party scripts into your flow page. This is commonly used for:
- Analytics tracking — Google Analytics, Mixpanel, PostHog
- Ad pixels — Meta Pixel, Google Ads conversion tags, TikTok Pixel
- Chat widgets — Adding a live chat overlay on top of the flow
- Heatmap tools — Hotjar, Microsoft Clarity
- Custom CSS — Overriding the flow’s default visual styles
How to add custom HTML:
- Navigate to Settings → Metadata → Custom HTML
- Choose the injection point:
<head> (for scripts that load early) or <body> (for scripts that run after the page loads)
- Paste your script or tag
- Click Save
- Republish the flow for changes to take effect
Only inject scripts from trusted, verified sources. Malicious or poorly written third-party scripts can break your flow, expose user data, or cause security vulnerabilities. ZappWay is not responsible for issues caused by custom HTML injections.
Custom Domains
Connect your own domain to remove the default zappflux.zappway.ai branding from your flow’s public URL and present a fully white-labeled experience to your users.
Example:
Default URL: https://flows.zappflux.zappway.ai/your-flow
Custom Domain: https://chat.yourcompany.com/your-flow
Setting Up a Custom Domain
Step 1: Add the domain in ZappWay
- Navigate to Settings → Custom Domains
- Click Add Domain
- Enter your desired domain or subdomain (e.g.,
chat.yourcompany.com)
- Click Add
Step 2: Configure DNS at your domain provider
- Log in to your domain registrar (GoDaddy, Cloudflare, Namecheap, etc.)
- Go to your DNS management panel
- Add a new CNAME record with the following values:
| Field | Value |
|---|
| Type | CNAME |
| Name / Host | chat (or your chosen subdomain prefix) |
| Value / Target | cname.zappflux.com |
| TTL | 3600 (or “Auto”) |
Step 3: Wait for verification
- DNS propagation typically takes between 5 minutes and 48 hours
- ZappWay checks the domain automatically and issues an SSL certificate once verified
- The domain status in your settings will update from Pending to Active
SSL certificates are provisioned automatically at no extra cost. You do not need to upload or manage certificates manually.
Domain Status Indicators
| Status | Meaning |
|---|
| Pending | DNS record has been added in ZappWay but not yet verified |
| Verifying | ZappWay is checking the DNS record |
| Active | Domain is live, SSL is provisioned, flow is accessible |
| Failed | DNS record could not be verified — check your CNAME configuration |
Troubleshooting Custom Domains
If your domain remains in Pending or Failed status:
- Double-check the CNAME record at your DNS provider — typos are the most common cause
- Ensure there are no conflicting A records for the same subdomain
- Wait up to 48 hours for full global DNS propagation
- Use a DNS checker tool (e.g.,
dnschecker.org) to verify the CNAME is resolving to cname.zappflux.com
- Contact support@zappway.ai if the issue persists after 48 hours
Collaborators
Invite team members to access and edit a specific flow without granting them access to your entire ZappWay organization.
Permission Levels
| Role | Permissions |
|---|
| Viewer | Can view the flow editor and settings in read-only mode; cannot make changes |
| Editor | Can edit flow blocks, settings, and metadata; can publish the flow |
| Admin | Full access including managing collaborators and deleting the flow |
Inviting a Collaborator
- Navigate to Settings → Collaborators
- Click Invite Collaborator
- Enter the team member’s email address
- Select their permission level (Viewer, Editor, or Admin)
- Click Send Invite
The invited user receives an email with a link to accept the invitation. If they don’t have a ZappWay account, they’ll be prompted to create one.
Managing Existing Collaborators
- Change Role: Click the role dropdown next to a collaborator’s name and select a new role
- Remove Access: Click the ⋮ menu next to the collaborator and select Remove
- Resend Invite: If an invitation has expired, click Resend next to the pending invite
Collaborators added at the flow level only have access to that specific flow. For broader organization-level access, manage team members in Settings → Team.
Global Integrations
The Integrations tab within Flow Settings is where you configure API credentials and connection tokens used by integration blocks throughout the flow. These credentials are stored securely and shared across all blocks within this flow.
Available Integrations
AI & Language Models
| Integration | Required Credential | Used For |
|---|
| OpenAI | OpenAI API Key | ChatGPT blocks, AI response generation, content classification |
| Anthropic | Anthropic API Key | Claude AI blocks for advanced reasoning and conversation |
How to add your OpenAI API Key:
- Navigate to Settings → Integrations → OpenAI
- Click Connect
- Paste your API key from platform.openai.com/api-keys
- Click Save
Google Services
| Integration | Required Credential | Used For |
|---|
| Google Sheets | Google OAuth (sign in with Google) | Read/write rows in spreadsheets via the Sheets block |
| Google Analytics | Measurement ID (GA4) | Send events from the Analytics block |
| Google Calendar | Google OAuth | Check availability, create events |
Messaging Channels
| Integration | Required Credential | Used For |
|---|
| WhatsApp (Evolution API) | API URL + API Key | Send messages via Evolution API provider |
| WhatsApp (WPPConnect) | API URL + Session Token | Send messages via WPPConnect provider |
| Telegram | Bot Token | Connect a Telegram bot to your flow |
Automation & Webhooks
| Integration | Required Credential | Used For |
|---|
| Zapier | Webhook URL (from Zapier) | Trigger Zaps from within the flow |
| Make (Integromat) | Webhook URL (from Make) | Trigger Make scenarios from within the flow |
Customer Support
| Integration | Required Credential | Used For |
|---|
| Chatwoot | API URL + Access Token | Transfer conversations to a Chatwoot inbox for human handoff |
Email
| Integration | Required Credential | Used For |
|---|
| SMTP | Host, Port, Username, Password | Send transactional emails via your own mail server |
| SendGrid | SendGrid API Key | Send transactional emails via SendGrid |
API keys and credentials stored here are scoped to this flow only. If you need the same credentials across multiple flows, you must configure them individually in each flow’s Settings. Organization-wide credential management is available on Enterprise plans.
Testing Integrations
After saving credentials, use the Test Connection button next to each integration to verify the credentials are valid before publishing your flow. A green checkmark confirms the connection is working; a red error indicates an issue with the credentials.
Publishing & Versioning
Publishing a Flow
Changes made in the flow editor are saved automatically as drafts. They are not visible to end users until you publish.
To publish:
- Complete your changes in the flow editor
- Click Publish in the top-right corner of the editor
- A confirmation appears indicating the flow is live
What publishing does:
- Makes the current draft version live at the flow’s public URL
- Saves a version snapshot (accessible in Version History)
- Notifies connected channels that a new version is available
Version History
Access previous published versions of your flow:
- Navigate to Settings → Versions
- A list of all published versions appears with timestamps
- Click any version to preview it
- Click Restore to roll back to a previous version
Before making major changes to a live flow, create a duplicate. Use the Duplicate Flow option from the flow list to make a safe copy, edit the copy, and publish it only when ready.
Troubleshooting
Issue: Custom HTML Script Not Firing
Symptoms:
- Analytics events not appearing in your tracking platform
- Pixel not registering conversions
Solutions:
- Ensure the flow has been republished after saving the custom HTML
- Verify the script is injected in the correct location (
<head> vs. <body>)
- Check the browser console (F12) for JavaScript errors from the script
- Test in an incognito window to rule out browser extensions blocking the script
- Confirm the script syntax is valid — a single error can prevent all custom scripts from running
Issue: Integration Test Fails
Symptoms:
- “Connection failed” error when testing an integration
- Blocks that use the integration throw errors at runtime
Solutions:
- Verify the API key or token has not expired or been revoked
- Check that the API key has the required permissions/scopes (e.g., OpenAI key must have chat completions access)
- For OAuth integrations (Google), try disconnecting and reconnecting your account
- Ensure there are no extra spaces before or after the pasted credential
- Contact support@zappway.ai with the integration name and error message
Issue: Collaborator Did Not Receive Invite
Symptoms:
- Team member says they never received the invitation email
Solutions:
- Ask them to check their spam/junk folder
- Verify you entered the correct email address in the invite
- Click Resend next to the pending invite in Settings → Collaborators
- If the issue persists, the team member can try signing up directly at zappway.ai with that email address, then you can retry the invite
Best Practices
1. Fill In Metadata Before Sharing
Always complete the Page Title, Description, and OG Image before sharing a flow link externally. A complete, polished preview builds trust and improves engagement.
2. Use Custom Domains for Client-Facing Flows
If you’re building flows for clients or running professional campaigns, always configure a custom domain. It reinforces brand identity and avoids confusion from the ZappWay subdomain.
3. Scope Collaborator Access Carefully
Grant Editor access only to users who need to make changes. Use Viewer access for stakeholders who need visibility without risk of accidental edits.
4. Rotate API Keys Periodically
For security, rotate API keys (OpenAI, Stripe, etc.) every 90 days. When you update a key, update it in Settings → Integrations and test the connection before republishing.
5. Republish After Every Settings Change
Changes to metadata, custom HTML, and integration credentials only take effect for end users after you publish the flow. Get in the habit of republishing immediately after saving settings changes.
Pro Tip: Use the Custom HTML field to inject a Hotjar or Microsoft Clarity session recording script on high-traffic flows. Watching real session recordings reveals exactly where users hesitate, drop off, or get confused — giving you actionable data to improve completion rates.
Support
Need help with Flow Settings?
Contact ZappWay Support:
- Email: support@zappway.ai
- Include: Flow name or ID, screenshot of the issue, and steps to reproduce
Provide These Details When Reporting Issues:
- Which settings section you were in (General, Metadata, Domain, etc.)
- The exact error message if one appeared
- Whether the issue affects one flow or all flows
- Your browser and operating system
Last Updated: March 2026
Platform: ZappFlux Flow Settings | ZappWay Dashboard