Skip to content
Eclipse Accounting Docs

Integrations

Integrations

Section titled “Integrations”

Integrations are where Eclipse does its most valuable automation work. Connect the systems you already use, then let the platform sync orders, transactions, and operational details into accounting workflows.

The integrations hub starts with operational health before marketplace browsing. Use it to check blocked reconnects, stale sources, first-sync work, and active syncs for connected banks, payment processors, and sales channels.

The dashboard uses the same health states in Connected sources, so blocked or stale integrations are visible before you open the integrations hub.

Bank transaction review also shows transaction-intake health for Shopify, Stripe, Amazon, and bank feeds. Month-end close and Import & Export show the same source-readiness states before you finalize a period or start import work. If a source is blocked, stale, waiting for its first sync, or currently syncing, Eclipse shows that status before you rely on imported rows.

Open a connected source’s settings to review its last sync, next scheduled sync, recent sync runs, and the scoped Sync now action when that connector supports manual refreshes.

Before a manual sync starts, Eclipse previews the selected scope, recent failures, last successful run, expected side effects, and blockers like an active sync or reconnect requirement.

Use the connected source’s own Sync now action for manual refreshes. The Analytics refresh can run active eBay and Shopify sources; other connectors direct you back to their integration page instead of reporting an empty sync as successful. Starting an eBay or Shopify refresh requires permission to manage integrations, and a locked or failed run stays visible as unsuccessful.

When a connection needs attention, Eclipse groups bank and integration issues into a tapered reminder cycle. Each email stage is saved before delivery, so a worker retry reuses the same recipient, issue summary, and delivery identity instead of creating a second reminder. If the provider outcome cannot be confirmed safely, Eclipse stops that stage for review rather than repeatedly sending it.

For connectors using realtime provider events, Eclipse verifies the provider request and stores an organization-bound event before acknowledging delivery. Provider retries reuse the stored event, while processing failures follow a bounded retry path and eventually stop in a reviewable dead-letter state instead of being treated as successful imports.

eBay and Shopify order retries reuse the same order and line records inside the connected workspace. A person who belongs to more than one workspace can import the same provider order identity independently, and a line cannot be attached to an order owned by another workspace.

Need another connection? Reach out through the app so the team can point you to the current best path.