Checking an integration before you buy

An integration page shows what we know about how two products connect, and which company stands behind each part of it. Use it to narrow your shortlist and to prepare your questions. It does not replace asking the vendors.

Make a list of the data your team needs to move, such as models, RFIs or schedules, and which way each one must go. Then open the integration page for the two products and switch to the Detailed view if it is not already on.

Check that each type of data you need is listed, in the direction you need. Rows sit under headings such as "Sends to (other product)", "Receives from (other product)" and "Syncs both ways". Directions are told from the product on the left. Reading an integration page shows where everything sits.

Each type of data carries one of four labels. Here is what each one means for a buying decision.

Label	What it tells you	What to do
Listed by AEC Integrations	We recorded it from public sources. Neither company has confirmed it.	Treat it as a lead. Check it against each vendor's documentation, and ask both vendors.
Confirmed by (a company)	That company stands behind it. The other company has not answered.	Ask the company that has not answered. If the label reads "Confirmed by one company", ask both.
Confirmed by both companies	Two different companies have each confirmed it.	This is the strongest label we show. Still check the details that matter to you, such as the versions you run.
Companies disagree	One company has confirmed it and the other has said it is not accurate.	Ask both vendors before you rely on it.

A label is a statement by the companies. We do not test integrations. The Sources button on a row shows who said what. Agreement states covers each label in full.

It tells you that we found the integration in public sources, such as vendor documentation, API references and integration marketplaces, and recorded it. Most rows on the site read this way today.

It does not tell you:

• that either company has confirmed it,
• that it works with the editions or versions you use,
• that it is still current,
• that we have tested it.

It is not a warning either. A row reads this way until a company at one end confirms it. A row where a company has said it is not accurate, and nobody has confirmed it, reads this way too, so open Sources to check.

Ask both companies, not just the one you are buying from. Their answers can differ.

• Does the integration work with the editions and versions we use?
• Which types of data move, in which direction, and how often?
• Who builds and supports it? The "Offered by" line on the page names the company we have on record.
• Does it pass through a connector product? If so, the page says "Through" and names it. Ask who supports that part.
• What does it cost, and what does setting it up involve?

• Offered by names the company you get the integration from.
• Last checked gives the date the integration was last checked, where there is one. Many integrations have no date yet.
• Vendor maintained or AEC Integrations maintained says who keeps the page up to date. It does not say who offers the integration.

If a row looks wrong, or an integration you rely on is missing, tell us with Suggest a correction on either product's page. See Requests and corrections.

• Previous: Reading an integration page.
• Next: How listings are classified.
• Agreement states.