# Make Evaluate Make credits, scenario recovery, access and CRM handoffs. Canonical page: https://quillwell.com/guides/software/make/ Updated 2026-11-05 Publisher: Quillwell Guides (https://quillwell.com/guides/about/). Editorial standards: https://quillwell.com/guides/editorial/ ## The short answer - This guide is based on vendor documentation checked November 5, 2026; we have not tested the product or its integrations. - Make is a candidate for branching visual workflows where the team can configure error handling and monitor credit consumption. - [Make](https://help.make.com/credits) bills credits; operations are module runs. Most operations use one credit at the default rate, but exceptions apply; some AI features depend on tokens or the connection. - [Make](https://help.make.com/incomplete-executions) says storing incomplete executions is disabled by default. Decide how failed submissions will be recovered before launch. ## Model credits per lead [Make](https://help.make.com/credits) defines an operation as a module run and bills credits. Most app operations use one credit at the default rate; [If-else and Merge](https://help.make.com/if-else-and-merge) use operations without credits. Third-party AI apps generally use one credit per operation, while Make AI Provider usage can include token-based credits. A custom provider can also bill its own tokens separately. Estimate polling checks, bundles, branches, lookups and writes for a representative form submission. Multiply by peak volume, then add retry and AI usage. Ask for the exact plan, allowance, renewal and billing treatment before quoting a cost. [Make](https://help.make.com/extra-credits) documents paid extra credits and optional automatic purchasing. Verify the account’s current price, purchase limit and behavior when credits run out; an enabled top-up can preserve execution while increasing spend. ## Configure failure storage and retries [Make](https://help.make.com/incomplete-executions) says incomplete execution storage must be enabled in scenario settings. Its [Retry error handler](https://help.make.com/retry-error-handler) can store a failed bundle and remaining flow for manual or automatic retry. Configure and test the path; do not assume a failed form submission is queued for recovery by default. [Make’s scenario settings](https://help.make.com/scenario-settings) say instant-trigger scenarios can deactivate on the first error despite the errors-before-deactivation setting. The same guide describes parallel webhook processing by default and an option to process in order. Choose ordering and alerts for the downstream CRM. A retry after an ambiguous timeout may repeat a write that the CRM already accepted. Use a stable source ID and an idempotent upsert where supported; inspect the destination and reconcile before replaying. Test an unavailable endpoint and a malformed field. [Make](https://help.make.com/manage-incomplete-executions) says an incomplete execution retry starts at the failed module with its original configuration, and the scenario must be active. Errors requiring configuration changes may need manual resolution. [Make](https://help.make.com/rollback-error-handler) says rollback can revert changes only in transaction-supporting modules. Auto-commit settings also affect which changes can be reverted; an email or other unsupported action cannot be assumed undone. See [Make’s illustrated incomplete-executions guide](https://help.make.com/manage-incomplete-executions) for the vendor’s screenshot of its recovery list. ## Set team boundaries [Make](https://help.make.com/teams) says scenarios, connections and webhooks belong to a team, and that plans below Teams have one team without managed roles in that team. Map each client or business unit to an access boundary before sharing credentials. [Make](https://help.make.com/custom-roles) says custom roles are Enterprise-only and permissions apply across the relevant resource type in a team. Separate teams where individual scenario-level restrictions are required, and verify the exact edition. ## Verify the form and CRM handoff [Make’s HubSpot CRM app](https://apps.make.com/hubspotcrm) lists search, create, update and Create or Update Contact modules. It requires a HubSpot Super Admin to pre-approve the app, including new scopes on reauthorization. The catalog does not establish the matching key for its upsert; verify it with the actual connector and account. Map a form submission ID, consent and campaign parameters into the CRM alongside the contact fields. Confirm the CRM accepts and routes the record, rather than treating a scenario’s completed status as proof of sales acceptance. Test duplicates, rate limits, changed permissions and empty fields. Document who owns each connection, the alert destination, history access and how to reconcile unprocessed submissions. Check whether a blueprint, logs and source data are sufficient for migration; do not assume a workflow export transfers credentials. [HubSpot](https://developers.hubspot.com/changelog/crm-api-write-validation-enforcement) says CRM API writes using its 2026-09 version enforce administrator-configured required and conditional properties. User-level OAuth association changes can also require permission. Confirm the connector’s API version and test validation errors; HubSpot says required associations remain enforced in the app UI, not public API writes. [Make’s webhook guide](https://help.make.com/webhooks) says webhook-specific logs are kept for three days, or 30 days on Enterprise. This is distinct from scenario execution history. Confirm retention and how to investigate a missing lead before launch. ## How to compare the alternatives Compare [Zapier](https://quillwell.com/guides/software/zapier/) and [n8n](https://quillwell.com/guides/software/n8n/) using the same inputs and failure cases. The [Zapier vs Make comparison](https://quillwell.com/guides/compare/zapier-vs-make/) contrasts costs and recovery. See [form builders](https://quillwell.com/guides/form-builder-software/) and [CRM software](https://quillwell.com/guides/crm-software/) for the endpoints. ## Common questions ### Are credits the same as operations? [Make](https://help.make.com/credits) bills credits. Most operations use one credit at the default rate, but exceptions apply: [If-else and Merge](https://help.make.com/if-else-and-merge) use operations without credits, and some AI usage depends on additional factors. ### Are failed runs stored automatically? [Make](https://help.make.com/incomplete-executions) says storing incomplete executions is disabled by default. Enable and test the appropriate recovery configuration. ## Sources and scope We read the linked vendor documentation on November 5, 2026. This is documentation-only research; we have not used these products, executed workflows or tested integrations. Inclusion and corrections are free; sponsorship does not determine our conclusions. Confirm current terms and test your own configuration. Sponsorship never changes this page. [How we research](https://quillwell.com/guides/editorial/). ## Sources 13 vendor pages, checked November 5, 2026 [Make: Credits](https://help.make.com/credits) Checked 2026-11-05. Credits, operations and AI usage. [Make: If-else and merge](https://help.make.com/if-else-and-merge) Checked 2026-11-05. Operations and credits for If-else and Merge. [Make: Extra credits](https://help.make.com/extra-credits) Checked 2026-11-05. Extra-credit purchasing and cost. [Make: Incomplete executions](https://help.make.com/incomplete-executions) Checked 2026-11-05. Storage of failed runs and default setting. [Make: Retry error handler](https://help.make.com/retry-error-handler) Checked 2026-11-05. Incomplete execution and retry behavior. [Make: Scenario settings](https://help.make.com/scenario-settings) Checked 2026-11-05. Ordering, deactivation and commit settings. [Make: Teams](https://help.make.com/teams) Checked 2026-11-05. Team ownership and plan restrictions. [Make: Custom roles](https://help.make.com/custom-roles) Checked 2026-11-05. Role availability and team-wide permissions. [Make: Manage incomplete executions](https://help.make.com/manage-incomplete-executions) Checked 2026-11-05. Retry starting point and original configuration. [Make: Rollback error handler](https://help.make.com/rollback-error-handler) Checked 2026-11-05. Transaction-supported modules and auto-commit limits. [HubSpot: CRM API write validation](https://developers.hubspot.com/changelog/crm-api-write-validation-enforcement) Checked 2026-11-05. Version-specific required properties and permission checks; required associations remain UI-only. [Make: HubSpot CRM app](https://apps.make.com/hubspotcrm) Checked 2026-11-05. Supported contact modules, approval and authorization requirements. [Make: Webhooks](https://help.make.com/webhooks) Checked 2026-11-05. Webhook log retention, distinct from scenario history. [Suggest a correction or send a vendor fact update](https://quillwell.com/guides/request/?type=correction&page=/software/make/)