Connect after-submit actions
Recorded walkthroughs: Copy a workflow and Diagnose & retry a failed workflow.
Open the form's workflow designer. Add the actions needed after submission, connect them in order and map their inputs. Start with a small graph and verify each action before adding branches.
Typical actions include email, HTTP/webhook calls, approval, calculations, variables and account/group operations. See the illustrated workflow node reference for every available node and its purpose.
Create native Umbraco Members
From MegaForm 2.0.68, select Native under Account system on Create User, Create Role and Add User to Role. On Umbraco these create a Member, ensure a Member Group and assign the Member to that group using the native Umbraco services. The same node types use DNN Users/Roles and Oqtane Users/Roles on those hosts.
Choose an existing Member Type alias on Create Member (default Member). Map username and email, and use the site's password policy. New nodes leave Update if exists off; enable it only when profile updates are intended. Running creation again reuses the member; it never resets an existing member's password. A membership that already exists succeeds without creating a duplicate.
These are public website Members, not backoffice accounts. Use the site's standard member login. Automatic login is DNN-only, and a welcome email is a separate Send Email action. Member Groups do not have the Description/System role properties of DNN roles.
Saved nodes without an account-system setting retain HostDefault. On Umbraco that is the original MegaForm web-account adapter (MF_WebUsers, MF_WebRoles, MF_WebUserRoles). Upgrading does not move accounts or change those workflows. To adopt native Members, explicitly select Native on all account and group nodes, review the mappings and test the full workflow; existing MegaForm web accounts are not migrated automatically.
Route approvals
Choose the intended approver or role, configure the decision paths and publish the workflow. Submit a QA entry, then sign in as an assigned reviewer and open My Inbox. Approve and reject separate test entries to verify both paths.
Make the task description useful without exposing unnecessary personal data. Confirm that an unrelated user cannot open the same task or entry.
Inspect failures and retry carefully
Open the entry's execution history to see the failing action, message and attempt. Correct its configuration or destination before using a supported manual Retry. A retry should add an attempt to history; it should not erase the original failure.
External systems may already have processed part of a workflow. Use an idempotency key such as the submission ID when the receiver supports it.
See Webhooks for HTTP mappings, Reports for diagnostics and C# scripting when configured actions cannot express the required logic.