The Guide IndexThe Guide Index

Topic

Automation & CRM

Connect tools that don't talk to each other, and get email into a CRM without logging your whole life.

Map trigger behavior, item bundles, currency units, duplicate handling and error recovery before enabling a workflow. These guides explain documented steps and usage estimates; they do not establish production reliability or actual monthly cost.

Local workbench

Automation workflow usage and cost calculator. Model tasks, credits, executions and quoted plan costs with three reproducible workflows. Explicit polling, bundle and retry assumptions.

Follow the workflow

  1. 01Check why HubSpot contacts keep duplicatingFirst identify the creation path and the unique identifier it uses.
  2. 02Send Shopify orders to Google Sheets with one row per line item (Make)Use Make’s Shopify trigger, an Iterator on line items and Add a Row so each item maps to its own spreadsheet row. Model polling, retries and bundle counts separately.
  3. 03Log paid Stripe Checkout sessions to Google Sheets with MakeLog selected paid Checkout sessions while preserving raw amounts and currency. Sheets search-and-append is not atomic, and row writing and thank-you status need separate tracking.

Keep useful records

  1. 01Audit a HubSpot export before deleting the old accountTreat the export as unproven until you can find representative records, their matching keys and the associations your destination needs.
  2. 02Log Gmail to HubSpot's free CRM automatically, including emails you didn't startConnect your inbox, set the account's contact email logging rule, tune the Gmail extension, and fill the Never log list, so client emails land on the right contact without logging your accountant or your mum.

Prepare a transfer

  1. 01Export HubSpot records without forgetting associationsChoose the records and associations deliberately.
  2. 02Use HubSpot Record IDs to update instead of duplicatingUse the existing Record ID when you intend to update a known HubSpot record.

Plan exception handling

  1. 01Balance Make execution logs against confidential-data needsMake can hide processed payloads from execution logs with “Keep data confidential”, but its documentation warns that troubleshooting options then become limited.
  2. 02Plan Make incomplete-execution storage before errors pile upDecide whether failed data must be retained, then monitor the storage used for incomplete executions.
  3. 03Retry a failed Make run without blindly creating duplicatesInspect both the failed execution and the destination before retrying.
  4. 04Choose sequential processing for a Make webhook workflowUse ordered processing when one run must finish before the next begins, but understand the queueing trade-off.

Compare approaches

  1. 01Make vs Zapier: model workflow units before pricing a planCompare explicitly modeled standard tasks and one-credit module runs. Branches, bundles, advanced tariffs and plan eligibility need separate checks. Counts are not a price quote.
  2. 02Zapier alternatives: compare Make, n8n and staying putMake and n8n use different billing units from Zapier. Reconstruct one real workflow before comparing a credit, execution or task. Staying with a working Zap can be better than paying migration and maintenance costs.

Open the complete article index · Search within Automation & CRM