Directoryz

Explain integrations by the task they support

An integration listing should tell visitors what moves between systems and what work it enables. A pair of logos rarely answers those questions.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Describe source, destination, direction, setup requirement, and the task. Link to supporting documentation for the claimed behavior.

Worked example · illustrative

What this looks like

A one-way export to a reporting tool is different from two-way contact synchronization and should be described accordingly.

Before you move on

Can a visitor tell whether the integration supports their actual workflow?

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 →