{"id":4473,"date":"2024-04-14T10:16:10","date_gmt":"2024-04-14T02:16:10","guid":{"rendered":"https:\/\/webflow.tenten.co\/?p=4473"},"modified":"2024-04-14T10:16:10","modified_gmt":"2024-04-14T02:16:10","slug":"webflow-logic-summary","status":"publish","type":"post","link":"https:\/\/webflow.tenten.co\/en\/webflow-logic-summary\/","title":{"rendered":"Webflow Logic Summary"},"content":{"rendered":"\n<div class=\"docs_rich-text w-richtext\">\n<p>Utilizing Webflow Logic enables you to build and execute automated sequences (referred to as &#8220;flows&#8221;) that gather and direct potential sales prospects, engage with your clientele, oversee your website content, and more \u2014 all through the Webflow Designer interface.\u00a0<\/p>\n<p>This tutorial covers the following:<\/p>\n<ol role=\"list\">\n<li>Accessing Logic<\/li>\n<li>Creating and organizing flows<\/li>\n<li>Implementing fallbacks<\/li>\n<li>Testing a flow<\/li>\n<li>Publishing flows<\/li>\n<li>Renaming, duplicating, and deleting flows<\/li>\n<li>FAQs and problem-solving suggestions<\/li>\n<\/ol>\n<h2>Accessing Logic<\/h2>\n<p>To kick off with Webflow Logic, simply click on the <strong>Logic<\/strong> icon located in the left sidebar to reveal the <strong>Logic panel<\/strong>. From there, navigate to the <strong>Flows<\/strong> tab to review general details about your flows (e.g., flow name, trigger, trigger source, status, etc.) and utilize the <strong>Flow editor<\/strong> for constructing, managing, and testing flows.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755146_64820f377bb824d4fdeaf6f0_f3ec956f.png\" title=\"64b94bc1917b8bf70a755146_64820f377bb824d4fdeaf6f0_f3ec956f\"><\/div>\n<\/figure>\n<h2>Creating and Organizing Flows<\/h2>\n<p>Flows consist of three key components: triggers, actions, and conditions. Begin crafting a new flow by accessing the <strong>Logic panel<\/strong> &gt; <strong>Flows<\/strong> tab and hitting <strong>New flow<\/strong> to enter the <strong>Flow editor<\/strong>.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755157_64820f44bdd3956bb10a7f36_7164dc38.png\" title=\"64b94bc1917b8bf70a755157_64820f44bdd3956bb10a7f36_7164dc38\"><\/div>\n<\/figure>\n<p>In the <strong>Flow settings<\/strong> section, allocate a <strong>title<\/strong> and <strong>description<\/strong> to your new flow for clarification and distinction. Here, you&#8217;ll also identify your <strong>Flow ID<\/strong>, which serves as the flow&#8217;s identifier for troubleshooting purposes.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94ba16bd63379357cacdd_6480bad1896fd74aebefb82c_8043f156.png\" alt=\"The Flow settings show the flow name set to \u201cRoute contact form submissions\u201d and description set to \u201cDirect contact form submissions to the appropriate mailbox.\u201d\u00a0\" title=\"64b94ba16bd63379357cacdd_6480bad1896fd74aebefb82c_8043f156-1\"><\/div>\n<\/figure>\n<p>Proceed with structuring your flow by selecting a trigger, then drag and drop actions and tools to the connection spots on the <strong>Flow editor<\/strong> canvas.<\/p>\n<blockquote><p><strong>Essential:<\/strong> While building your flow, a yellow \u201c<strong>wrench<\/strong>\u201d icon will display on each block until its settings are configured. Once configured, the yellow \u201c<strong>wrench<\/strong>\u201d is swapped with a green \u201c<strong>checkmark<\/strong>\u201d icon.<\/p><\/blockquote>\n<h6><strong>Point to Note:<\/strong> Leaving the <strong>Flow editor<\/strong> without saving will keep the flow in draft mode with your modifications preserved.<\/h6>\n<p>You can rearrange blocks within your flow by dragging and dropping them to different connection points. Blocks can also be removed from the flow by right-clicking and choosing <strong>Remove block<\/strong>, or by selecting and hitting <strong>Delete <\/strong>on your keyboard.<\/p>\n<h3>Triggers<\/h3>\n<p>Each flow initiates with a trigger \u2014 an occurrence either within your site (e.g., form submission) or externally (e.g., webhook event) that commences the flow.<\/p>\n<p>To integrate a trigger to your flow, click on <strong>Select a trigger starting this flow<\/strong> and opt for the desired trigger. There are two trigger choices:<\/p>\n<ul role=\"list\">\n<li><strong>Form submission<\/strong> \u2013 activated upon form submission on your Webflow site<\/li>\n<li><strong>Incoming webhook<\/strong> \u2013 triggered by an event in an external platform<\/li>\n<\/ul>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755170_64820f721d0809f2e7e596a8_160dee65.png\" title=\"64b94bc1917b8bf70a755170_64820f721d0809f2e7e596a8_160dee65\"><\/div>\n<\/figure>\n<h6><strong>Reminder:<\/strong> Each flow can only have one trigger.\u00a0<\/h6>\n<p>After adding a trigger, select the trigger block on the canvas, input a name under <strong>Trigger name<\/strong>, and configure the trigger settings based on its type (e.g., Form submission or Incoming webhook).<\/p>\n<p>To replace or remove the trigger from your flow, right-click the trigger and choose <strong>Remove trigger<\/strong>, or select it and press <strong>Delete <\/strong>on your keyboard.<\/p>\n<p>Examine the output of your trigger (i.e., data shared with subsequent blocks) in <strong>Trigger settings <\/strong>&gt; <strong>Output<\/strong> tab.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a75515a_64820f82af8419aa99bd6bb5_fc4b0f24.png\" alt=\"The Output tab of Trigger settings displays all of the information the trigger shares with subsequent blocks in the flow.\" title=\"64b94bc1917b8bf70a75515a_64820f82af8419aa99bd6bb5_fc4b0f24\"><\/div>\n<\/figure>\n<p>Subsequent to the trigger, you can execute actions (e.g., Send email notification, Create CMS item, Invite user, etc.) or establish conditions using tools.<\/p>\n<h4>Form submission<\/h4>\n<p>If employing a Form submission trigger, initiate by adding a form to your site. Connect your flow&#8217;s trigger to the designated form, prompting the flow to engage upon user form submission.\u00a0<\/p>\n<blockquote><p><strong>Important:<\/strong> Each form can serve as a trigger for one flow exclusively; it can&#8217;t be used for multiple Logic flows.\u00a0<\/p><\/blockquote>\n<p>To link a form to your flow:<\/p>\n<ol role=\"list\">\n<li>Open the <strong>Flow editor<\/strong><\/li>\n<li>Select the <strong>Form submission trigger <\/strong>block to reveal <strong>Trigger settings<\/strong><\/li>\n<li>Choose the form from the dropdown menu<\/li>\n<\/ol>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a75517d_64820f93ee09d974435e0f48_1d293c91.png\" alt=\"The Form dropdown in Trigger settings allows you to select a form on your site to connect to your flow.\" title=\"64b94bc1917b8bf70a75517d_64820f93ee09d974435e0f48_1d293c91\"><\/div>\n<\/figure>\n<p>To incorporate a Form submission trigger from the Designer canvas, select the form, access <strong>Element settings panel <\/strong>&gt; <strong>Form settings<\/strong> &gt; <strong>Source<\/strong>, change <strong>Source<\/strong> to <strong>Logic<\/strong>, and choose either <strong>Add new flow<\/strong> or <strong>Browse flows<\/strong> to link the form to a new or existing flow.\u00a0<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755189_64820fa75554f2901245572b_e9de3b43.png\" alt=\"The option to add a new flow or browse existing flows appears in Form settings when the Source is set to Logic.\" title=\"64b94bc1917b8bf70a755189_64820fa75554f2901245572b_e9de3b43\"><\/div>\n<\/figure>\n<p>To detach a form from your form submission trigger, access the <strong>Flow editor<\/strong>, &#8230;and proceed to <strong>Activate settings<\/strong> &gt; <strong>Form<\/strong> drop-down and tap on <strong>Unlink form<\/strong>.\u00a0<\/p>\n<h6><strong>Important: <\/strong>If desired, you can activate spam filtering on your website to screen form entries for spam. Discover more about spam filtering.\u00a0<\/h6>\n<h4>Receiving webhook<\/h4>\n<p>The Receiving webhook switch permits you to transfer real-time data from external applications (e.g., Airtable, Make, Twilio, etc.) to your flow in JSON form. Essentially, the Receiving webhook switch empowers your external apps to communicate with your flow.\u00a0<\/p>\n<p>To employ a Receiving webhook switch, duplicate your <strong>Webhook URL<\/strong> from the switch settings, then insert it in the third-party application which will direct requests to this webhook. For instance, you could send a webhook from Mailchimp which would then start your Logic flow.\u00a0<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755174_64820fbdfc0a1a398ad1a9f5_91854f36.png\" title=\"64b94bc1917b8bf70a755174_64820fbdfc0a1a398ad1a9f5_91854f36\"><\/div>\n<\/figure>\n<h6><strong>Important:<\/strong> Receiving webhook switches necessitate the utilization of external third-party utilities to communicate with the webhook. Kindly contact the third-party utility directly for assistance or functionality inquiries.\u00a0<\/h6>\n<h3>Activities\u00a0<\/h3>\n<p><strong>Activity blocks<\/strong> enable you to specify what you wish your flow to perform. They may optionally receive input data, execute a segment of reasoning, and always produce output data (i.e., information that will be shared with subsequent blocks).\u00a0<\/p>\n<p>You can scrutinize the output data (i.e., the information that the block shares with successive blocks in the flow) of <strong>Activity blocks<\/strong> in <strong>Block settings<\/strong> &gt; <strong>Output<\/strong> tab.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a75517a_64820fc885c0b4c147b2bcef_c39a7a11.png\" title=\"64b94bc1917b8bf70a75517a_64820fc885c0b4c147b2bcef_c39a7a11\"><\/div>\n<\/figure>\n<p>Let\u2019s explore the obtainable <strong>Activity blocks<\/strong>:\u00a0<\/p>\n<ul role=\"list\">\n<li>Distribute email alert<\/li>\n<li>Generate CMS element<\/li>\n<li>Eliminate CMS element<\/li>\n<li>Modify CMS element<\/li>\n<li>Look for CMS elements<\/li>\n<li>Initiate HTTP request<\/li>\n<li>Summon user<\/li>\n<li>Erase user record<\/li>\n<li>Revise user record<\/li>\n<\/ul>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755162_64820fd6ca50308063801cdf_ad524eb8.png\" title=\"64b94bc1917b8bf70a755162_64820fd6ca50308063801cdf_ad524eb8\"><\/div>\n<\/figure>\n<h4>Distribute email alert\u00a0<\/h4>\n<p>The <strong>Distribute email alert<\/strong> block authorizes you to send a custom email alert to any content editors on your site or individuals of your Workspace upon triggering the flow.\u00a0<\/p>\n<p>Select the block in the <strong>Flow editor<\/strong> and navigate to <strong>Distribute email alert block settings<\/strong>. Afterwards, tap into the <strong>Transfer to<\/strong> field to pick specific collaborators from the pool of accessible collaborators, or choose <strong>All collaborators<\/strong> to dispatch an email alert to all contributors on the list.\u00a0<\/p>\n<h6><strong>Important: <\/strong>If you wish to dispatch email alerts to individuals who are not members of your Workspace, you&#8217;ll need to either incorporate them into your site as content editors or forward your data to an external email service using the Initiate HTTP request block. Find out more about inviting content editors to your site.<\/h6>\n<p>You can personalize the subject line and message of the email using varied data from your trigger. The ensuing data types can be employed in the subject and message fields:\u00a0<\/p>\n<ul role=\"list\">\n<li>Straightforward<\/li>\n<li>Electronic mail<\/li>\n<li>Cellphone<\/li>\n<li>Number<\/li>\n<li>Text Zone<\/li>\n<li>Checkmark<\/li>\n<li>Timestamp<\/li>\n<\/ul>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a75515f_6482100e0656fd83d0dce159_c24da844.png\" alt=\"The subject and message of the Send notification email block contain custom messages using the dynamic name, email address, and message inputs from form submissions.\" title=\"64b94bc1917b8bf70a75515f_6482100e0656fd83d0dce159_c24da844\"><\/div>\n<\/figure>\n<p>To cease receiving email notifications, click the \u201c<strong>garbage<\/strong>\u201d icon beside their name.\u00a0<\/p>\n<h4>Generate CMS element\u00a0<\/h4>\n<p>The <strong>Generate CMS element<\/strong> block empowers you to concoct a fresh CMS element within a Compilation when the block is triggered. The block settings will present the fields existing in the chosen Compilation.\u00a0<\/p>\n<h6><strong>Important: <\/strong>Ensure you&#8217;ve set up a CMS Compilation prior to configuring your flow to certify you can attach your <strong>Generate CMS element<\/strong> block to the Compilation.\u00a0<\/h6>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a75516b_64821021b10705d01335ad84_cf793d30.png\" alt=\"The Create CMS item block settings displays the fields available in the selected Collection.\" title=\"64b94bc1917b8bf70a75516b_64821021b10705d01335ad84_cf793d30\"><\/div>\n<\/figure>\n<blockquote><p><strong>Essential: <\/strong>Please be mindful of privacy implications when incorporating data into the CMS. For instance, if you collect leads and establish CMS elements based on those leads, those items are included in your sitemap and anyone with a read-only preview link for your site could view them. You should noindex any dynamic pages that shouldn&#8217;t be visible to site visitors or indexed by search engines. Discover more about disabling search engine indexing and optimum methods for privacy.<\/p><\/blockquote>\n<p>With this block, you can correlate fixed input <em>or<\/em> dynamic data from your flow (e.g., trigger data from form submissions or block output data) directly to your CMS Compilation\u2019s basic info and personalized fields. You can only correlate like data kinds together (e.g., data from a plain text field in a form can only be correlated to a plain text field in the CMS). Assisted bindings cover:\u00a0<\/p>\n<div class=\"w-embed\">\n<div role=\"table\" aria-label=\"Supported CMS bindings\" class=\"w-layout-grid product-page_size-tbl\">\n<div role=\"rowgroup\">\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"columnheader\" class=\"product-page_size-table-cell cc-header\">Form field type<\/span><span role=\"columnheader\" class=\"product-page_size-table-cell cc-header\">CMS field type(s)<\/span><\/div>\n<\/div>\n<div role=\"rowgroup\">\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Plain text<\/span><span role=\"cell\" class=\"product-page_size-table-cell\">Plain text (includes name and slug)<\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Number<\/span><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Number, plain text (includes name and slug)<\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Checkbox<\/span><span role=\"cell\" class=\"product-page_size-table-cell\">Switch (true\/false), plain text (includes name and slug)<\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Email<\/span><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Email, plain text (includes name and slug)<\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Phone<\/span><span role=\"cell\" class=\"product-page_size-table-cell\">Phone, plain text (includesname and alias)<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n<h6><strong>Remark: <\/strong>Presently we do not endorse the mapping from a plain text field to a link-type field in the CMS. We also do not back fields created using custom components.<\/h6>\n<blockquote><p><strong>Crucial: <\/strong>You might observe a yellow \u201c<strong>wrench<\/strong>\u201d icon emerge beside your variables as you link them to your CMS Collection fields. This \u201c<strong>wrench<\/strong>\u201d icon adjacent to a variable suggests that you require to define a fallback for that variable. Learn more about utilizing fallbacks.<\/p><\/blockquote>\n<p>You can also designate the CMS item to draft status, stage it for publication, or publish the live item when the flow is initiated. Find out more about publication options.<\/p>\n<h4>Erase CMS item\u00a0<\/h4>\n<p>The <strong>Delete CMS item<\/strong> block permits you to eradicate a CMS item within a Collection when the block is activated. You can delete by CMS item ID or opt for a CMS item by name.\u00a0<\/p>\n<h6><strong>Remark: <\/strong>Maintain that you\u2019ve formed a CMS Collection and sample items before configuring your flow to ensure you can connect your <strong>Delete CMS item <\/strong>block to the Collection.\u00a0<\/h6>\n<h4>Revise CMS item\u00a0<\/h4>\n<p>The <strong>Update CMS item<\/strong> block enables you to modify a CMS item\u2019s fundamental information and custom fields by CMS item ID or by CMS item name using static input <em>or<\/em> dynamic data from your flow (e.g., trigger data from form submissions or block output data).\u00a0<\/p>\n<h6><strong>Remark: <\/strong>Ensure that you\u2019ve generated a CMS Collection and Collection items prior to arranging your flow to ensure you can link your <strong>Update CMS item <\/strong>block to the Collection.\u00a0<\/h6>\n<p>Similar to the <strong>Create CMS item<\/strong> block, you can associate your form data directly to your CMS Collection\u2019s fundamental information and custom fields. You can solely associate like data types together (e.g., data from a plain text field in a form can solely be linked to a plain text field in the CMS). Supported linkages encompass:\u00a0<\/p>\n<div class=\"w-embed\">\n<div role=\"table\" aria-label=\"Supported CMS linkages\" class=\"w-layout-grid product-page_size-tbl\">\n<div role=\"rowgroup\">\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"columnheader\" class=\"product-page_size-table-cell cc-header\">Form field type<\/span><span role=\"columnheader\" class=\"product-page_size-table-cell cc-header\">CMS field type(s)<\/span><\/div>\n<\/div>\n<div role=\"rowgroup\">\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Plain text<\/span><span role=\"cell\" class=\"product-page_size-table-cell\">Plain text (embraces name and alias)<\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Number<\/span><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Number, plain text (embraces name and alias)<\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Checkbox<\/span><span role=\"cell\" class=\"product-page_size-table-cell\">Switch (true\/false), plain text (embraces name and alias)<\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Email<\/span><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Email, plain text (embraces name and alias)<\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Phone<\/span><span role=\"cell\" class=\"product-page_size-table-cell\">Phone, plain text (embraces name and alias)<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n<h6><strong>Remark: <\/strong>At present, we do not support mapping from a plain text field to a link-type field in the CMS. We also do not endorse fields made using custom components.<\/h6>\n<blockquote><p><strong>Crucial: <\/strong>You might observe a yellow \u201c<strong>wrench<\/strong>\u201d icon emerge beside your variables as you link them to your CMS Collection fields. This \u201c<strong>wrench<\/strong>\u201d icon adjacent to a variable name suggests that you require to set a fallback for that variable. Learn more about utilizing fallbacks.<\/p><\/blockquote>\n<p>You can uphold the current status of the CMS item you\u2019re altering or set it to draft status, stage it for publication, or publish the live item when the flow is initiated. Find out more about publication options.<\/p>\n<h4>Find CMS items\u00a0<\/h4>\n<h6><strong>Remark:<\/strong>\u00a0Collections containing obligatory fields that aren\u2019t supported in Logic aren\u2019t feasible for use in the Search for CMS items block.<\/h6>\n<p>The <strong>Search for CMS items<\/strong> block enables you to explore for CMS items by CMS item ID or by name using data from your flow. This permits you to execute actions using data from the retrieved CMS item later on in your flow, which can be advantageous for sites with user-generated content or marketing sites that collect leads.\u00a0<\/p>\n<p>For instance, if you constructed a cookbook site that permits site visitors to submit recipes, you could search for recipes in the CMS using the recipe name from your form submission and then, utilizing the <strong>Conditional rule<\/strong> utility block and <strong>Send email notification<\/strong> blocks, send the submission to site editors if an existing recipe with that name is found. Then, site editors can eliminate\/combine the identical recipes.<\/p>\n<blockquote><p><strong>Crucial: <\/strong>If no item is unearthed in a Search for CMS items block followed by a Conditional rule utility block, the flow halts at the Search for CMS items block and does not execute subsequent actions.\u00a0<\/p><\/blockquote>\n<h4>Make HTTP request\u00a0<\/h4>\n<p>The <strong>Make HTTP request<\/strong> block connects Webflow Logic and your external tech stack (e.g., Mailchimp, Airtable, etc.) by permitting you to automate HTTP requests to any RESTful API endpoint. Then you can execute actions using the response data later on in your flow.\u00a0<\/p>\n<p>Learn more about the Make HTTP request block.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755190_6482105e3e0f727c7c5a755e_d52012bd.png\" alt=\"The Make HTTP request block settings include authentication, request methods, URL, request headers, and request body.\" title=\"64b94bc1917b8bf70a755190_6482105e3e0f727c7c5a755e_d52012bd\"><\/div>\n<\/figure>\n<h4>Invite user\u00a0<\/h4>\n<p>The <strong>Invite user<\/strong> block permits you to automate inviting users to your User Accounts site and allocating them to access groups. This block functions well, for instance, with a Form submission trigger linked to a lead generation form that allows site visitors to indicate their desire for a user account.<\/p>\n<h6><strong>Remark: <\/strong>The <strong>Invite user<\/strong> block is exclusively accessible on sites with User Accounts enabled. Learn more about User Accounts.<\/h6>\n<h4>Delete user account\u00a0<\/h4>\n<p>The <strong>Delete user account<\/strong> block permits you to automate removing users from your User Accounts site by user ID or user email. You can also pick an existing user on your site.<\/p>\n<h6><strong>Remark: <\/strong>The <strong>Delete user account <\/strong>block is solely available on sites with User Accounts enabled. Learn more about User Accounts.<\/h6>\n<h4>Modify user account\u00a0<\/h4>\n<p>The <strong>Update user account<\/strong> block permits you to alter a user\u2019s preferences (e.g., for marketing communications) and access groups by user ID or user email. You can also select an existing user on your site to adjust their preferences.<\/p>\n<h6><strong>Remark: <\/strong>The <strong>Update user account<\/strong> block is solely accessible on sites with User Accounts enabled. Learn more about User Accounts.<\/h6>\n<h3>Tools<\/h3>\n<p>The <strong>Conditional rule<\/strong> utility block allows you to establish conditions that determine the subsequent actions in your flow: If condition A, then execute action B \u2013 but if condition C, then carry out action D.\u00a0<\/p>\n<p>In essence, you can formulate a condition and designate actions to occur if the condition is fulfilled (i.e., actions willtake place on the \u201ctrue\u201d path) and if the condition is not satisfied (i.e., actions will happen on the \u201cfalse\u201d path). This enables you to automate email notifications, HTTP requests, manage CMS Collection items, and more, based on rules from the flow\u2019s trigger setting or output data.\u00a0<\/p>\n<p>For instance, if you insert a <strong>Conditional rule <\/strong>utility block after a form submission trigger, you can establish conditional rules based on output data (e.g., name, email, etc.) from form submissions. To delve deeper into this illustration, you could set up a rule that triggers a section of your flow if someone named Mike Wazowski submits your form. In case Mike Wazowski submits your form, then a specific part of your flow would be executed, but if anyone else (not named Mike Wazowski) submits your form, another segment of your flow would be executed.\u00a0<\/p>\n<h6><strong>Note:<\/strong> Actions do not have to be defined on both the \u201ctrue\u201d and \u201cfalse\u201d paths. For instance, if you wish to generate a CMS item when a form is submitted with the \u201cname\u201d field specified, solely include the <strong>Create CMS item<\/strong> action on the \u201ctrue\u201d path. The \u201cfalse\u201d path (which will be executed when the form is submitted without a value in the \u201cname\u201d field) has no actions and will remain idle.\u00a0<\/h6>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a75513e_6482108cb1e611601001f051_2c5a5d7b.png\" title=\"64b94bc1917b8bf70a75513e_6482108cb1e611601001f051_2c5a5d7b\"><\/div>\n<\/figure>\n<p>You have the ability to create conditional rules based on output data from <em>all<\/em> preceding blocks in your flow. For instance, if you design a flow where a form submission triggers a <strong>Search for CMS items<\/strong> action block, your <strong>Conditional rule<\/strong> utility block can incorporate data from form submissions <em>and<\/em> data from CMS items.\u00a0<\/p>\n<p>This can be advantageous for websites with user-generated content or marketing sites that gather leads. For example, on a cooking website that permits visitors to submit recipes, you could establish conditional rules to redirect recipe submissions to different Collections (e.g., \u201cBreakfast,\u201d \u201cAppetizers,\u201d \u201cDesserts\u201d) based on the dish type. Or, on a marketing website that captures sales leads, you could search for existing leads in the CMS using the company name from form submissions and then either create or update leads in the CMS based on the company name.\u00a0<\/p>\n<p>To configure a <strong>Conditional rule<\/strong> utility block, choose the block, then navigate to <strong>Conditional rule settings<\/strong> &gt; <strong>Condition<\/strong>. Pick a field from the <strong>Select field<\/strong> dropdown, and then a type of logic from the<strong> Select logic <\/strong>dropdown (e.g., Is set, Is empty, Ends with, etc.).\u00a0<\/p>\n<p>The following field types are available for utilization in the <strong>Select field <\/strong>dropdown:<\/p>\n<ul role=\"list\">\n<li>Plain text<\/li>\n<li>Email<\/li>\n<li>Phone<\/li>\n<li>Number<\/li>\n<li>Text area<\/li>\n<li>Checkbox<\/li>\n<li>Select<\/li>\n<li>Radio button<\/li>\n<\/ul>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755177_64821099346ca96d21fa051f_baa1807b.png\" alt=\"The Select logic dropdown in Conditional rule settings allows you to select a type of logic to create a conditional rule.\" title=\"64b94bc1917b8bf70a755177_64821099346ca96d21fa051f_baa1807b\"><\/div>\n<\/figure>\n<p>If you\u2019ve opted for a type of logic (also referred to as an \u201coperator\u201d) that necessitates a comparison (e.g., Equals, Contains, Starts with, etc.), an <strong>Enter text<\/strong> field will materialize. Here, you\u2019ll have to either input your desired text or incorporate a variable by clicking the purple \u201c<strong>dot<\/strong>\u201d icon in the field. Find out more about available operators in Logic.<\/p>\n<p>The variables you\u2019ll be able to access in this field will vary depending on the initial field (i.e., data type) and type of logic you\u2019ve selected. In the aforementioned example of the marketing site, we would form a comparison to ascertain whether \u201ccompany name\u201d in the form matches or includes \u201cname\u201d in the CMS item. The variables in this context are \u201ccompany name\u201d and \u201cname.\u201d\u00a0<\/p>\n<blockquote><p><strong>Important: <\/strong>All comparisons are case sensitive. For example, if the condition is \u201cName <strong>Contains<\/strong> G,\u201d \u201cGr\u00edmur\u201d returns true, but \u201cgr\u00edmur\u201d returns false.\u00a0<\/p><\/blockquote>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755149_648210aa4e00b644d7d54c43_24f72f99.png\" alt=\"An example conditional rule in Conditional rule settings: Run the true branch if the \u201cname\u201d field in the form submission matches the \u201cname\u201d field in the CMS Collection.\" title=\"64b94bc1917b8bf70a755149_648210aa4e00b644d7d54c43_24f72f99\"><\/div>\n<\/figure>\n<p>You can disconnect your fields or logic at any moment by selecting the <strong>Condition <\/strong>dropdown and then selecting <strong>Unlink<\/strong>.\u00a0<\/p>\n<h4>Available operators\u00a0<\/h4>\n<p>Let\u2019s explore the available types of logic, or \u201coperators,\u201d for each data type:\u00a0<\/p>\n<div class=\"w-embed\">\n<div role=\"table\" aria-label=\"Logic operators\" class=\"w-layout-grid product-page_size-tbl\">\n<div role=\"rowgroup\">\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"columnheader\" class=\"product-page_size-table-cell cc-header\">Data type<\/span><span role=\"columnheader\" class=\"product-page_size-table-cell cc-header\">Operators<\/span><\/div>\n<\/div>\n<div role=\"rowgroup\">\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Plain text<\/span><span role=\"cell\" class=\"product-page_size-table-cell\"><\/p>\n<ul>\n<li>Is set<\/li>\n<li>Is not set<\/li>\n<li>Equals<\/li>\n<li>Does not equal<\/li>\n<li>Contains<\/li>\n<li>Does not contain<\/li>\n<li>Starts with<\/li>\n<li>Does not start with<\/li>\n<li>Ends with<\/li>\n<li>Does not end with<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Number<\/span><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\"><\/p>\n<ul>\n<li>Is set<\/li>\n<li>Is not set<\/li>\n<li>Equals<\/li>\n<li>Does not equal<\/li>\n<li>Is greater than<\/li>\n<li>Is less than<\/li>\n<li>Is greater than or equal<\/li>\n<li>Is less than or equal<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Option<\/span><span role=\"cell\" class=\"product-page_size-table-cell\"><\/p>\n<ul>\n<li>Is set<\/li>\n<li>Is not set<\/li>\n<li>Equals<\/li>\n<li>Does not equal<\/li>\n<li>Contains<\/li>\n<li>Does not contain<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Boolean (also known as \u201cSwitch\u201d in the Webflow Designer)<\/span><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\"><\/p>\n<ul>\n<li>Is true<\/li>\n<li>Is false<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Phone<\/span><span role=\"cell\" class=\"product-page_size-table-cell\"><\/p>\n<ul>\n<li>Is set<\/li>\n<li>Is not set<\/li>\n<li>Equals<\/li>\n<li>Does not equal<\/li>\n<li>Contains<\/li>\n<li>Does not contain<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Email<\/span><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\"><\/p>\n<ul>\n<li>Is set<\/li>\n<li>Is not set<\/li>\n<li>Equals<\/li>\n<li>Does not equal<\/li>\n<li>Contains<\/li>\n<li>Does not contain<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Link<\/span><span role=\"cell\" class=\"product-page_size-table-cell\"><\/p>\n<ul>\n<li>Is set<\/li>\n<li>Is not set<\/li>\n<li>Contains<\/li>\n<li>Does not contain<\/li>\n<li>Starts with<\/li>\n<li>Does not start with<\/li>\n<li>Ends with<\/li>\n<li>Does not end with<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Shade<\/span><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\"><\/p>\n<ul>\n<li>Matches<\/li>\n<li>Differs<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Clip link<\/span><span role=\"cell\" class=\"product-page_size-table-cell\"><\/p>\n<ul>\n<li>Comprises<\/li>\n<li>Doesn&#8217;t encompass<\/li>\n<li>Begins with<\/li>\n<li>Does not initiate<\/li>\n<li>Concludes with<\/li>\n<li>Does not conclude with<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\">Choose<\/span><span role=\"cell\" class=\"product-page_size-table-cell cc-colored\"><\/p>\n<ul>\n<li>Matches<\/li>\n<\/ul>\n<p><\/span><\/div>\n<div role=\"row\" class=\"product-page_size-table-row\"><span role=\"cell\" class=\"product-page_size-table-cell\">Wireless button<\/span><span role=\"cell\" class=\"product-page_size-table-cell\"><\/p>\n<ul>\n<li>Matches<\/li>\n<\/ul>\n<p><\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n<h6><strong>Observation: <\/strong>The <strong>Is set<\/strong> operator checks if a variable (e.g., form input value) exists. It will return &#8220;false&#8221; if the text comprises solely blank spaces. The <strong>Is empty<\/strong> operator verifies if a variable (e.g., form input value) contains non-empty data. It will return &#8220;true&#8221; if the variable holds data or only whitespace characters. In case a visitor submits a form with only spaces in an input field (e.g., the \u201cname\u201d field), a condition using <strong>Is empty<\/strong> for the input field would return &#8220;true&#8221; and execute the &#8220;true&#8221; branch of the flow, while a condition with <strong>Is set<\/strong> would return &#8220;false&#8221; and activate the &#8220;false&#8221; branch of the flow.<\/h6>\n<h2>Employing fallbacks<\/h2>\n<p>Fallbacks are default values used instead of a variable if the variable is inaccessible. Fallbacks are necessary when handling data from Incoming webhook triggers or from Form submission triggers where form field inputs are not mandatory. A yellow &#8220;wrench&#8221; symbol next to a variable indicates the need for a fallback.<\/p>\n<p>Imagine you devised a plan that generates CMS items using data from a form submission that triggers the process. Your aim is to name the CMS items based on the data from the \u201cname\u201d field in the form, which isn&#8217;t obligatory. If the \u201cname\u201d field remains empty in the form submission, the designated fallback will be utilized to name the CMS item. As an example, setting a fallback as \u201cNo name provided\u201d and a visitor submits the form without entering \u201cname,\u201d your CMS item would then be named \u201cNo name provided.\u201d<\/p>\n<p>To set a fallback for a variable:\u00a0<\/p>\n<ol role=\"list\">\n<li>Tap the yellow \u201cwrench\u201d symbol next to the variable name<\/li>\n<li>Enter a fallback value, or click the violet \u201cdot\u201d symbol to opt for another variable as a fallback<\/li>\n<\/ol>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755186_648210bff97c1131d0cfa8f3_8e25cfa8.png\" title=\"64b94bc1917b8bf70a755186_648210bff97c1131d0cfa8f3_8e25cfa8\"><\/div>\n<\/figure>\n<p>To eliminate a fallback for a variable:<\/p>\n<ol role=\"list\">\n<li>Choose the variable with the intended fallback to exclude<\/li>\n<li>Erase the fallback value from the <strong>Fallback<\/strong> field<\/li>\n<\/ol>\n<h2>Ways to evaluate a flow<\/h2>\n<p>It&#8217;s prudent to evaluate a flow before releasing it to confirm proper configuration of blocks and to ensure smooth flow execution. This practice also aids in troubleshooting flow-related issues.<\/p>\n<p>To assess a flow, select <strong>Test<\/strong><strong>flow<\/strong> at the upper right corner of the <strong>Flow editor<\/strong>. This opens a modal menu where you can input sample data for the connected trigger to execute the flow. After entering the data, click <strong>Run test<\/strong> to initiate the test flow. The test outcome will be displayed in the modal menu post-test completion.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a75518d_648210dd708de903e4096c7c_277ade65.png\" alt=\"Test result in the modal menu window: \u201cTest has been successful! Status: 200.\u201d\" title=\"64b94bc1917b8bf70a75518d_648210dd708de903e4096c7c_277ade65\"><\/div>\n<\/figure>\n<p>You can individually test <strong>Make HTTP request<\/strong> blocks outside the main flow. Right-click on the <strong>Make HTTP request<\/strong> block and choose <strong>Test this action<\/strong>, or select the block on the canvas and tap <strong>Run test<\/strong><strong>to complete setup<\/strong> in Block settings \u2014 leading you to a modal menu to input sample data for the utilized values.\u00a0<\/p>\n<p>Following data entry, click <strong>Run test<\/strong> to execute the test for this block. The results are displayed in the modal menu post-test completion. Click <strong>Apply data<\/strong> to utilize the test response for evaluating the rest of the flow.<\/p>\n<h3>Operate history<\/h3>\n<p>Operation history offers a log detailing the outcomes of both successful and unsuccessful previous runs of flows. To access Operation history, navigate to <strong>Flow editor<\/strong> &gt; <strong>History<\/strong> tab. Clicking on any timestamp in Operation history reveals the input data that triggered that specific flow run.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a75514e_6482110ef584da25bd555793_bcb28a80.png\" title=\"64b94bc1917b8bf70a75514e_6482110ef584da25bd555793_bcb28a80\"><\/div>\n<\/figure>\n<h2>Steps to finalize flows<\/h2>\n<p>The procedure for finalizing your flow varies based on the trigger used to initiate the flow (e.g., Form submission or Incoming webhook). If your flows don&#8217;t interact with site elements, you can independently manage flow finalization from site publishing (excluding flows triggered by Form submissions, as they rely on site forms).<\/p>\n<h6><strong>Important:<\/strong> Publishing flows to a single domain is not feasible. Flows must be published across all domains connected to your site.<\/h6>\n<blockquote><p><strong>Essential: <\/strong>If your flow encompasses blocks affecting CMS items (e.g., Create CMS item, Delete CMS item, etc.) and you modify the CMS Collection schema (e.g., adding or removing a Collection field), reconfiguration of your flow and staging it for publishing becomes necessary.<\/p><\/blockquote>\n<h4>Finalizing a Form submission flow<\/h4>\n<p>To finalize your flow utilizing a Form submission trigger, first choose the triggering form from the <strong>Form<\/strong> dropdown in the <strong>Flow editor<\/strong>. For publishing the flow during the next full site release, tap <strong>Publish<\/strong>, then <strong>Stage flow for publish<\/strong>.<\/p>\n<blockquote><p><strong>Essential:<\/strong> If any changes are made to the form linked with the form submission trigger (e.g., adding or removing fields), reissuing the site publication is mandatory to guarantee that the revised form is available for use in the flow.<\/p><\/blockquote>\n<p>You can also immediately retract the flow from the live site by tapping <strong>Publish<\/strong> and then <strong>Unpublish flow<\/strong>.<\/p>\n<p>If you attempt to publish your site while unresolved issues with any flows persist, an alert modal will appear listing flows encountering unresolved issues. If you decide to publish the site without addressing them, any flows with unresolved issues will be deactivated.<\/p>\n<h4>Publishea New incoming webhook mechanism<\/h4>\n<p>Unlike procedures that utilize Form submission triggers, procedures that utilize New incoming webhook triggers do not necessarily necessitate the publication of your site.\u00a0<\/p>\n<p>There are 2 alternatives for disseminating procedures that use New incoming webhook triggers:\u00a0<\/p>\n<ul role=\"list\">\n<li>If you desire to make the procedure live on your active site immediately, tap <strong>Release<\/strong> and then <strong>Deploy procedure now<\/strong><\/li>\n<li>If you aim to unveil the procedure on your forthcoming full site release, click <strong>Release<\/strong> and then <strong>Arrange procedure for release<\/strong><\/li>\n<\/ul>\n<p>You are able to engage <strong>Deploy procedure now<\/strong> in the <strong>Procedure editor<\/strong> anytime you wish to propagate fresh modifications to your procedure live \u2014 minus having to launch your full site on each occasion. Subsequent changes you implement to your procedure will not manifest on the active site until you tap <strong>Deploy procedure now<\/strong>.<\/p>\n<p>You can also retract your procedure from your active site instantaneously by clicking <strong>Release<\/strong> and then <strong>Eliminate procedure<\/strong>.<\/p>\n<p>If you endeavor to publish your site while there are pending matters with any of your procedures, an alert dialogue box will emerge with a register of procedures with unresolved concerns. If you proceed to launch your site without rectifying them, any procedures with pending matters will be rendered inactive.<\/p>\n<h2>Tips for modifying, duplicating, and removing procedures<\/h2>\n<p>You can pinpoint the alternatives to modify, duplicate, and erase procedures in the drop-down arrow menu adjacent to the procedure title.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755168_6482115b43001360d605e8e7_0abad592.png\" title=\"64b94bc1917b8bf70a755168_6482115b43001360d605e8e7_0abad592\"><\/div>\n<\/figure>\n<p>You can likewise modify your procedures by substituting the <strong>Procedure title<\/strong> in <strong>Procedure settings<\/strong>.\u00a0<\/p>\n<h6><strong>NB: <\/strong>To rename an individual block, you can input or replace the <strong>Block title<\/strong> in <strong>Block settings<\/strong>. To erase an individual block from your procedure, right-click on the block and select <strong>Delete block<\/strong>, or highlight the block and press <strong>Erase<\/strong> on your keyboard. Individual blocks are not able to be duplicated currently.\u00a0<\/h6>\n<h2>Frequently asked questions and problem resolution hints<\/h2>\n<h3>What is the maximum number of procedures permitted on my site?\u00a0<\/h3>\n<p>To avert performance setbacks, there is a cap of 20 procedures per site. If you make an attempt to establish more than 20 procedures on a site, you will be prompted to remove a procedure initially.\u00a0<\/p>\n<h3>How many conditional directives\/action blocks can be employed in a singular procedure?\u00a0<\/h3>\n<p>You can insert up to 50 blocks in a singular procedure. This encompasses the conditional block. An \u201cA maximum number of 50 blocks reached\u201d error message will materialize upon reaching the threshold.<\/p>\n<h3>Is Reasoning covered in my site\/Workspace arrangement?\u00a0\u00a0<\/h3>\n<p>You are not mandated to possess a site or Workspace plan to employ Reasoning, however, you might need a site or Workspace plan to boost your usage limits or the quantity of procedures you can devise. <a href=\"https:\/\/webflow.com\/pricing\">Refer to our plans and pricing page for insights on Reasoning usage constraints<\/a>.\u00a0<\/p>\n<h3>Which Workspace functions have the authorization to construct and oversee procedures?\u00a0<\/h3>\n<p>All Workspace functions have the authority to construct and manage procedures. Bear in mind that Workspace members with site-level <strong>Can design<\/strong> or <strong>Can design (Limited)<\/strong> roles are unable to publish full sites, thus, these Workspace members may necessitate aid from other members to publish procedures that interact with elements on the site (e.g., procedures that use Form submission triggers). Learn more about Workspace functions and permissions.\u00a0<\/p>\n<h3>Assistance needed! I am unable to enact alterations to my procedure!\u00a0<\/h3>\n<p>If you are utilizing a form submission trigger, ensure you have released your site subsequent to linking your procedure to the form or executing any alterations to the form. Upon releasing your site, you can click <strong>Arrange for release<\/strong> to implement alterations to your procedure on your next full site release.\u00a0<\/p>\n<p>If you have completed this already and are still incapable of enacting alterations to your procedure, verify that all block settings have been properly configured and the green &#8220;<strong>checkmark<\/strong>&#8221; icon is visible on all the blocks in your procedure. If a yellow &#8220;<strong>wrench<\/strong>&#8221; icon emerges anywhere in your procedure, this denotes that block settings still necessitate configuration.<\/p>\n<h3>What transpires when a form field employed in a procedure undergoes a modification?\u00a0<\/h3>\n<p>The live procedure will cease functioning. This predicament will occur if a form field is eradicated, appended, or renamed. You will need to reconfigure your procedure, prepare your procedure for release, and publish your site to rectify your live procedure.<\/p>\n<h3>My procedure was previously operational, but currently an exclamation point is displayed on my procedure trigger.\u00a0<\/h3>\n<p>If you are utilizing a form trigger and you have altered your form (e.g., altering the form title, adding or removing form fields, etc.), you will need to reset the form trigger to reconfigure your procedure. To accomplish this, pick your trigger in the <strong>Procedure editor<\/strong>, navigate to <strong>Trigger settings<\/strong>, and tap <strong>Reset the form trigger<\/strong>.<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94bc1917b8bf70a755183_6482118196e68c75e8ee3460_b69fad33.png\" title=\"64b94bc1917b8bf70a755183_6482118196e68c75e8ee3460_b69fad33\"><\/div>\n<\/figure>\n<h3>My action blocks are not functioning correctly.\u00a0<\/h3>\n<p>Kindly double-check that your block settings have been properly configured. In the situation of Make HTTP request blocks, ensure that your HTTP request and block settings have been structured correctly. If all block settings have been appropriately configured, endeavor republishing your site and applying changes to your procedure.\u00a0<\/p>\n<p>If republishing your site does not resolve your issue, please record your screen and <a href=\"https:\/\/webflow.typeform.com\/logic-feedback\">submit your issue to the Webflow Logic Bug and Feedback Form<\/a>. Ensure to include your <strong>Procedure ID<\/strong> with your submission.\u00a0<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow-s3.tenten.co\/2024\/04\/64b94ba16bd63379357cacdd_6480bad1896fd74aebefb82c_8043f156.png\" alt=\"The Procedure settings exhibit the procedure title set to \u201cRoute contact form submissions\u201d and description set to \u201cDirect contact form submissions to the appropriate mailbox.\u201d\u00a0\" title=\"64b94ba16bd63379357cacdd_6480bad1896fd74aebefb82c_8043f156-1\"><\/div>\n<\/figure>\n<h3>What transpires if a collaborator is eliminated from a site or Workspace subsequent to being appended to a Dispatch email notification block?\u00a0<\/h3>\n<p>The former collaborator will no longer receive emails from the Dispatch email notification block. Nonetheless, they will not be eradicated from the collaborator list in the Dispatch email notification block settings \u2014 manual removal is necessary.\u00a0\u00a0<\/p>\n<h3>Can Logic be employed to alter content or a design on my site?\u00a0<\/h3>\n<p>The Create CMS item and Update CMS item blocks can be utilized to modify content on the site when <strong>Create as<\/strong> is defined as <strong>Live<\/strong>. Note that the site necessitates a refresh to depict live modifications to CMS content.\u00a0<\/p>\n<p>However, except for those CMS-related blocks, you cannot utilize Logic to alter content or design on your site at this moment.\u00a0<\/p>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" src=\"https:\/\/webflow.tenten.co\/wp-content\/uploads\/2024\/04\/64b94bc1917b8bf70a755180_636966d4ad1d4fe8fa63e1f1_led8olyyklx79f7vbw-nflr8sgywganx_c0t8g9srkcwvgcv_li0bnwr3s50_vsedgv_tszfexpojdsdreth7m56hyxirei4uxutftk_rpdixpfz4gazt1e00suz5hcjrtoeuug1gnucxajcyvifm8.png\" title=\"64b94bc1917b8bf70a755180_636966d4ad1d4fe8fa63e1f1_led8olyyklx79f7vbw-nflr8sgywganx_c0t8g9srkcwvgcv_li0bnwr3s50_vsedgv_tszfexpojdsdreth7m56hyxirei4uxutftk_rpdixpfz4gazt1e00suz5hcjrtoeuug1gnucxajcyvifm8\"><\/div>\n<\/figure>\n<h3>WillWill the logic still function after I export my website?<\/h3>\n<p>The flow of logic (alongside CMS and Ecommerce content) is not embedded in the exported code. Logic operation relies on hosting for proper functionality.<\/p>\n<h3>Is it possible for other members in the Workspace to view any private information (like third-party API keys, usernames, and passwords) I have entered?<\/h3>\n<p>Workspace members can access, manage, and utilize credentials. Nonetheless, once a credential is generated, no one, even the original creator, can see the actual details of the credential in the Webflow UI. Essentially, Workspace members can view the customized names assigned to the credentials, but do not have the ability to access the actual keys or tokens.<\/p>\n<h3>How does Webflow store and manage credentials?<\/h3>\n<p>Credentials are securely stored &#8211; always encrypted during transmission and at rest. After a credential is established, no one, not even the originator, can view the true contents of the credential within the Webflow UI. Users can only see the user-defined titles for the generated credentials.<\/p>\n<p>Please be aware that despite the secure storage of credentials by Webflow, they do not have jurisdiction over any server or external service where you may transfer those credentials utilizing logic flows.<\/p>\n<h3>What happens to credentials during the cloning or transfer of a site?<\/h3>\n<p>Credentials are not preserved during the cloning or transfer of a site. Any credentials used in your processes will need to be set up anew once the site has been cloned or transferred.<\/p>\n<h3>If I duplicate a site from the gallery, will the flows be copied as well? Can I share flows through duplicable sites?<\/h3>\n<p>Absolutely. Duplicating a site equates to cloning it entirely. All elements tied to the site, including flows, will be replicated, except for credentials. Any credentials integrated into your processes will require reconfiguration post the cloning process.<\/p>\n<h3>Will the transferred site retain flows if I transfer a site with flows to another user?<\/h3>\n<p>Indeed. All components linked to the site, like flows, will be transferred, excluding credentials. Any credentials used in your processes will need to be set up once the site has been transferred.<\/p>\n<h3>What happens to flows when a site is recovered from a backup? Are they reinstated or left unaltered?<\/h3>\n<p>Restoring a backup will reinstate the flows to their state at the time of backup creation. However, due to possible divergences between your site&#8217;s forms and CMS schemas from the backup, recovered flows may potentially disrupt published processes.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"Make your sites more powerful and useful with native Webflow automation.","protected":false},"author":2,"featured_media":5320,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"om_disable_all_campaigns":false,"inline_featured_image":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"csco_display_header_overlay":false,"csco_singular_sidebar":"","csco_page_header_type":"","footnotes":""},"categories":[298],"tags":[],"class_list":{"0":"post-4473","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-logic","8":"cs-entry"},"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/posts\/4473","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/comments?post=4473"}],"version-history":[{"count":0,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/posts\/4473\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/media\/5228"}],"wp:attachment":[{"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/media?parent=4473"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/categories?post=4473"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/tags?post=4473"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}