# Create your own plugins

The plugin builder lets you design tables, references, views and workflows. Under **Data**, you work with saved records in your active plugin. You do not need to write code.

## Start with contacts

1. Open the [plugin builder](/account/plugins/build) and sign in.
2. Enter a name, such as “My contacts”, and choose **Use contacts template**. Name, company, email and processing status are already prepared.
3. If you need more tables, add them under **Data model** before the first activation. Then under **Data**, choose **Activate data** once. This installs the saved draft as a fixed release for your organization. You need organization owner or administrator rights. If you changed the template, choose **Save draft** first.
4. Use **Create record** to enter your first contact. **Create** saves it in the plugin, in the workspace selected at the top.
5. Click a value in the table, edit it and choose **Save**. Reload the page: the contact and its changes remain. **Open plugin** shows the same records outside the builder.
6. Use **Open** to open the contact. Run **Start**, then **Complete**, to move its status from New through In progress to Done. An invalid transition is refused with an explanation.

Access roles determine who can read or edit your contacts. Installing or publishing a plugin does not grant others access to these records.

## Edit the data model visually

Under **Data model**, every table appears as a card containing its fields. Lines show references between tables. Select a table name or field to open its settings. **Add table** adds another table; **Field** inside a card adds a field such as “Phone”.

Use **Reference** to add a field that links to records in a table. In the panel beside it, select the **Linked table** and whether it can link to one or multiple records. Selecting an existing reference opens the same settings. Drag cards by their handles or arrange them with the arrow keys; card positions are not saved.

You can also select a field through its column name under **Data**. Change its name, type, required setting or choices there. The text field used as the record title keeps its type. For a status that should change only through actions, select **Only workflows may change this** under **Initial value and editing**, and provide a suitable initial value.

### Example: link a contact to a company

Start with a new contacts draft that you have not activated yet. The existing **Company** field is a text field; add a reference to link to a separate company record.

1. Open **Data model**, choose **Add table**, name the table “Companies”, and confirm with **Create table**. Its **Title** field holds the company name.
2. Choose **Reference** in the contacts card. Name the new field “Company reference”, select the new table as the **Linked table**, and allow one record. A line now connects the two table cards.
3. Choose **Save draft**, then **Activate data** under **Data**.
4. Select Companies under **Table** and create a record with the company name in **Title**. Switch to contacts, then select that company in the new reference field when creating or editing a contact.
5. Save and reload the page. The reference remains and is also visible on the contact through **Open plugin**.

The picker shows only company records you can read. Several contacts can link to the same company. Adding a new table through an update is currently unsupported once the plugin is activated.

## Design forms and views

Under **Views**, select the view you want. **Design** presents its fields as editable blocks: columns in a table or a vertical stack in a form. Drag a field to its new position or use its arrow buttons. Hide fields from this view and restore them under **Show another field**. Hiding a field preserves the field and its data. Required fields stay visible in forms.

**Use view** opens the view with the same saved records as **Data**. A form creates real records in the selected workspace. It uses the active release; draft changes appear there after you activate the update.

The settings beside the canvas control the view name and field selection. A board groups a choice field; a calendar needs a date or instant field. Unchanged generated views include new fields automatically. Customized field selections and ordering stay intact. On narrow screens, settings open in a dialog; Escape closes it. Wide tables and the data model scroll horizontally.

## Apply changes

Field names, references and views are edited in your draft first. Choose **Save draft**, then **Activate changes**. If the plugin is already installed, the update review opens. The new release is used only after its preview and your confirmation. Until then, the data table keeps using the active release.

The update review supports labels, views and additional optional fields in existing tables, including new references to tables that are already installed. Define new tables before the first activation. Adding or removing tables later, changing existing field types or reference targets, adding permissions, expanding role permissions or changing workflows requires a separate migration that the builder does not currently offer. You can save those changes as a draft, but cannot apply them to the installed plugin.

If another tab saved first, your local edits remain in the editor. Export them under **Settings → Import / export** before reloading and reconciling the changes.

## Workflows and optional simulation

Under **Flows**, select a status transition or action. For a simple transition, set **State field**, **Allowed starting states** and **Target state**. **Add workflow** adds an action; **Advanced** contains inputs, conditions, permissions and ordered steps.

A workflow describes an action’s steps. A hook connects an internal event to a follow-up action. Execution checks current permissions and record state again. Recent runs on a record show the state of automatic follow-ups. Schedules, incoming webhooks and actions using Secrets/Integrations credentials are not available in the builder yet.

For an isolated test, open **Settings → Workflow simulation**. Save the draft first, then choose **Open simulation**. Only here are inputs temporary test data in the browser tab: they are not saved as contacts, exported or published. You can try roles and internal follow-ups. **Back to saved records** returns to the plugin.

## Share and work with an AI app

Under **Use plugin → Releases and publishing**, create a fixed release and find the link to publishing it in the Hub. Your plugin remains private until you explicitly publish it. The [Hub guide](/docs/plugin-hub) explains visibility, updates and exports.

Connect your AI app using the [MCP setup guide](/docs/connect), and reconnect after changes to the available tools. For example, ask: “Show my contacts in the contacts plugin whose status is New.” It uses the same plugin data within its permissions; general context search does not search plugin records. A personal connection can also prepare private drafts. Install and publish them in the browser.
