Directoryz

Distinguish native integrations from third-party workflows

Visitors need to know who provides and supports the connection. Treating all integrations as equivalent can hide setup or support differences.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Record the provider of the connection and any intermediary involved. Keep the distinction visible in the listing description or fields.

Worked example · illustrative

What this looks like

A native connection documented by the product differs from an automation recipe maintained by another service.

Before you move on

Can the visitor identify which company or tool supports the connection?

Write down the evidence for your answer. If you cannot point to a concrete example, revise the work before treating it as ready.

A repeatable workflow

  1. Start with a real information need.
  2. Inspect the page a visitor actually receives.
  3. Keep search observations separate from assumptions about cause.

Your working notes

Apply this guide to one real project. Notes stay in this page until you download them; they are not saved to your account.

Where Directoryz fits

Directoryz supports directory publishing, listings and custom fields, CSV imports, submission review, and workspace operations. These guides include editorial workflows you can carry out with a worksheet or your own tools. They do not imply that every audit, reminder, verification, or integration is automated by Directoryz.

Foundations and templates →