Tell us what you need to connect.

"We use System X" is a useful starting point, but a better request explains what information must move. For example, "Create an invoice in our accounting system when a job is approved, then return confirmed payment status." Include which direction the data should travel and how quickly updates matter.

Tell us whether you now export CSV files, retype records, use middleware, or depend on a custom application. Include the volume of records and which staff own exceptions. Do not send credentials or real customer files through an unapproved request form.

A request does not mean an integration exists or will be delivered on a specific date. The team should review feasibility, vendor API availability, security needs, and business value before promising a connection.

• Name source, destination, direction, frequency and required business action.
• Include example field names but no live credentials or customer data.
• Ask how failed writes will be surfaced and retried.
• Do not assume a requested connector has a delivery date or price.