What it is

A request is how you tell Tightly you want it to read from, or write to, a system it does not connect for you today. On Integrations every source Tightly connects by hand carries a Request button on its own page, for an admin or a member. Pressing it tells Tightly's team once, in a message to the team: which system, from which organisation, pressed by whom. Nothing is built by the press, nothing is stored against your organisation, and nothing is charged for it.

A request that becomes work is a record Tightly's team files for it, one per system name, and that record is where a request's state is written. Your press does not open that record by itself; a member of Tightly's team does. It is a staff record: you do not read it, and this book does not describe its pages.

How Tightly decides it

Nothing about a request runs on its own. Work begins when somebody at Tightly presses Start the build on the record, and that press is a person's, because each build spends money.

Five answers are what the record carries. An answer nobody gave is left blank rather than guessed at.

• What it is called. The system's own product name, as you say it.
• Who needs it. You, your company, and why.
• Which sets. What should feed Tightly, in the same set words a live connection already prints.
• Which direction. Whether the system should be your system of record or a second source beside one; and what should read back out of Tightly, from Purchase orders, Stock levels and Product data.
• A sandbox. Whether the vendor runs one, whether the vendor's own free account would do, whether you would let a read of your own account be recorded, or none of the three. Neither is an answer too, and it does not refuse the request.

Anything you already know about the system's own developer documentation is worth adding. A link from you decides what Tightly is allowed to read while it works the system out.

The words on the face

After a press the source's page reads Requested in State, with a Requested row carrying the day, and "{Name} is requested; Tightly will be in touch." (or "{Name} is requested." where a long name would not fit the line). The Request button is gone. That receipt lives on the page only: leave it or reload and the page reads Not connected again, and the Integrations list does not show it. The message has reached Tightly's team all the same. A press that did not go through says so where the button was, in the face's words where the server sent none:

The request for {Name} did not go through; try again.

What you can do about it

Settings, Integrations is the page. Open the source you want and press Request once. A system that is not on the list has no page, and so nothing to press; tell Tightly's team about it.

Ask Tightly can tell you, in this article's words, what a request asks for and point you at the button. It cannot file one: filing is your own press, or a Tightly team member's tool. Ask Tightly will not give you a date for a connection or say one is being built: it cannot read the record, and only the record says where a request stands.

Glossary line

A request is the press on a source's Integrations page that tells Tightly's team you want a system it connects by hand; a record is kept only once the team files one, and no date comes with it.