Integrations

Connect Stictr Build to your accounting/ERP system

Integrations are in early access

Connecting a system today securely stores and validates your credentials so you're ready the moment two-way sync ships for it. Live data sync is rolling out connector by connector — cards below show "Sync: Coming Soon" until it's live for that system.

E-Signature (DocuSign)

Checking connection…

Connect your company's own DocuSign account to send Commitments, Potential Change Orders, and Prime Contract Change Orders for real signature — each party's signature automatically advances the record's status when DocuSign reports it complete. Without a connection, these use manual signature tracking as before. Commitment Change Orders (CCOs) always use manual tracking.

Connection

Discovered capabilities

Select a connection above, connect it, and click "Discover Capabilities" to see which modules and objects are available — every customer's subscription/entitlements are different, so this is checked per connection, not assumed.

Sync domain settings

Choose which domains the selected connection is allowed to touch. This only controls what's enabled for a future sync — object sync itself isn't implemented yet for any connector (that's a later phase); this is groundwork the eventual sync engine will read.

Type

Type	Local value	External ID	External value	Match	Actions

—

1 / 1

Sync execution against provider objects isn't implemented yet for any connector — a run created here is tracked and stays pending until that work ships. This lets you exercise the run history/retry machinery now.

Sync runs

#	Trigger	Direction	Dry run	Status	Started	Finished	Actions

—

1 / 1

Two-step by design: a project manager requests a record be sent to the ERP once it's fully executed; nothing actually goes out until an Owner, Admin, or Accounting user approves it here. Approving queues the record for sync (live push still rolls out per connector — see the "Sync: Coming Soon" badges above).

Requested records

#	Record type	Local ID	Status	Requested	Actions

—

1 / 1

Conflict detection runs as part of incremental sync, which isn't implemented yet — this list will be empty until then. Resolution (below) is fully functional for any conflict that does exist.

Conflicts

#	Type	Detected	Status	Resolution	Actions

—

1 / 1