WeldConnect

WeldConnect

WeldConnect automates work across WeldSuite and the apps you connect. A workflow starts from a trigger (a record changes, a schedule fires, a webhook is called, another workflow finishes) and then runs its steps one after the other.

Create a workflow

Build, test and publish your first workflow.

Triggers

Record events, schedules, webhooks and chained workflows.

Logic steps

Conditions, loops, delays and approvals.

Runs and history

Follow runs, fix failures and restore older versions.


What you can do

  • Workflows: build automations in a visual editor, test them, then publish.
  • Triggers: start a run when a record is created or changed, on a schedule, from a webhook call, or after another workflow finishes. See Triggers.
  • WeldSuite steps: create companies, contacts, leads, deals and tasks, move deals, log activities, post to WeldChat, notify teammates, send email and call any API. See WeldSuite steps.
  • Logic: branch with conditions, repeat steps for each item in a list, wait, and pause for an approval. See Logic steps.
  • AI: generate text or classify it inside a run, with a credit limit per run. See AI steps.
  • Apps: post to Slack, write to Google Sheets, send from Gmail, create Google Calendar events and open GitHub issues. See Connect apps.
  • Runs: every run is recorded with its status, input, output and errors. See Runs and history.

The WeldConnect sidebar has Overview, Workflows and Executions, then Variables and Webhooks, and Analytics.


A workflow acts as its owner

The person who created a workflow is its owner. Every run acts on the owner's behalf: a step can only do what the owner's role allows, and that is checked each time the step runs, not only when you publish.

  • If the owner loses a permission (for example they can no longer create leads), steps that need it start failing with a clear message in the run.
  • If the owner leaves the workspace, the workflow's WeldSuite steps and app steps stop working. To take a workflow over, open the row menu on Workflows and choose Duplicate: you become the owner of the copy, which starts as a draft. Publish the copy and delete the original.
  • Steps that post to Slack, Google or GitHub use the workspace's connection to that app, not the owner's personal account. They still stop once the owner has left the workspace.

Tip

Build workflows that the whole team relies on from an account that stays in the workspace and has the permissions those steps need. Ask an admin to check the role under Team and permissions.


Templates

Open Templates in the WeldConnect sidebar to start from a ready-made workflow instead of a blank one. The gallery has two groups:

  • Starter templates: ready-made workflows for common jobs, such as following up on new leads, celebrating won deals in WeldChat, a weekly AI kickoff email or alerting you when a workflow fails.
  • Your templates: workflows your team saved with Save as template on a workflow's Settings page.

Each template shows whether it is ready to use or how many fields you still need to fill in, and which app connections it needs (for example Slack or Google Sheets). Use template creates a draft workflow and opens it in the editor; fill in the steps marked as needing setup, then publish it as described in Create a workflow.


Connectors

WeldConnect Connectors import live data from first-party apps (Shopify, WooCommerce, Moneybird, Stripe). After the first import, the provider pushes changes over webhooks; a periodic catch-up fills gaps.

  • Shopify / WooCommerce: products, orders, and customers.
  • Moneybird: contacts, sales invoices, products, and purchase invoices/receipts into WeldBooks. Moneybird stays the book of record: imported invoices and bills do not post to the WeldSuite ledger. It can also receive your Stripe sales: see Send Stripe sales to Moneybird.
  • Stripe: finalized invoices, payments, fees and payouts into WeldBooks.

Connect them from Settings → Integrations.


Next steps

Previous
Find and save leads