The question this page answers

What feeds Tightly, is it live, what synced when, what failed, what can I connect or ask for, and what reads from Tightly? Integrations is the list; every source opens onto its own connector page.

What you see

Integrations, filtered to Connected, with the table and the search marked 1 and 2.

1. 1Connected, what is live today, with State and Last sync.
2. 2Find an integration, the search that narrows Connected and Available.

With no system of record it reads "Nothing feeds Tightly yet." and offers one door, Connect your system of record, in Setup.

Connected is a table of what is live: Integration (with one sub-word where true: system of record, yours for your own mailbox, Publishes product data, Posts bills or Posts purchase orders), Role, State and Last sync. The state is one word: Connected, Syncing, Failed, Paused or Waiting for first sync. Last sync is a time and only a time; Never for a connection that has not run, Never syncs for a source Tightly stamps no sync for, such as Slack, Xero and SPS. Your mailbox has its own heading. Available lists everything else by name, grouped by kind: what sells, what runs the business, what moves the goods, then the rest, then Reads from Tightly, then any other system. A filter and a search, Find an integration, narrow both.

The row is the door. A connector page carries a Status card (State, Last sync, Last run, What failed, Setup, Takes, System of record, Role, Plan, Connected, the account it is connected to, Credentials and Access, each only where true; unconnected shows State, Role and, where they apply, Plan, Requested, Turnaround and Access). On a failed or quiet connection the sync health read's own sentence stands on the card. Beside it stand Checks, what the connection test tried, where it answered with checks; Feeds Tightly (Set, Reads, State, Fields, Last read, Rows), where Reads is On, Off, Off · recorded or Not offered and State is Not started, Syncing, Synced or Failed, with the served reason on hover; and Reads from Tightly (What, When, State, Last write, Refused). Beneath them stand Fields, one row per column the source sent (Field, Entity, Seen in, Use), once Tightly has kept a run; on the system of record Engine input coverage (Engine, Field coverage, Fields to review), each engine Available, Required fields, Optional fields or Review setup; and History, one row per sync, import, mapping, scope or dictionary change, drift or field added or removed.

What to do

The acts sit on the connector page, each with its consequence line first and its result in place.

1. Press Connect to take the source's credentials or send you to sign in at the provider; for Shopify you give the shop address and install the Tightly app in your Shopify admin.
2. Press Request to tell Tightly's team you want a system Tightly connects by hand.
3. Press Sync now to run the system of record's sync early.
4. Press Pause or Resume to stop or restart a Shopify sync.
5. Press Make this the system of record, after reading which engines read differently once you switch.
6. Press Reconnect to take new credentials without losing anything already synced.
7. Press Disconnect to stop a source.
8. Turn Stop reading or Read again on a set's row to change what the next sync takes; nothing already read is deleted.

The first system of record is connected in Setup; an organisation with none reads "Your first system of record is connected in Setup." A sync that does not yet filter sets records the choice and reads Off · recorded regardless. Match the fields opens the mapping wizard at that set. Publish product data here is a Shopify switch, offered where your plan includes publishing. Match locations matches a Cin7 location to a Tightly place; Set up EDI accounts opens the account book; Talk to us pauses or disconnects a connection Tightly set up for you.

Admins connect, sync, switch and disconnect; members may request, and read "Admins change this"; a read-only seat sees every fact and no button, with one reason on the Status card: "Your access is read-only; an admin can change it on Team."

API keys has its own article; the Product data API row under Reads from Tightly opens it. Webhooks has no row here.

When it is empty or failed

A failed read prints "The integrations did not load." with Try again; a connector page that did not load prints "{Name} could not be read." An address naming no known source prints "Tightly has no integration by that name." A card whose read did not answer says so, for example "What {Name} feeds Tightly was not read.", with Try again. A refused connection prints Tightly's sentence for it under the form, for example:

NetSuite refused these credentials. Check the Account ID first, exactly as Setup > Company Information shows it, then the Consumer Key, Consumer Secret, Token ID and Token Secret, and test again.

On Tightly Lite, Shopify is the one system you can connect here, and your mailbox connects on Email. A Connect on any other system is refused:

That system is not one this workspace can connect. Connect one from your integrations list, or talk to us about this one.

A source gated on something your plan does not hold is absent from the list on every plan but Tightly Pro, where it is listed and its page reads Not on your plan, with the plan that sells it on the Plan row.