Gateway to Your Data
Every Crust AI Snippet you create is fundamentally accessible via a unique Shareable URL. This web link is the gateway for your viewers to access the specific data view you’ve configured. Think of the URL not just as an address, but as a set of instructions telling Crust AI which snippet to load, how to display it initially, and potentially which specific record or user context applies.

Understanding how Snippet URLs are constructed is crucial for:

  • Sharing snippets effectively.
  • Integrating snippets into Airtable automations or button fields.
  • Using snippets within external workflow tools (Make, Zapier, n8n).
  • Building robust applications by linking multiple snippets together.

​
The Anatomy of a Snippet URL

A typical Crust AI Snippet URL follows this basic structure:

URL Structure Example
https://app.trycrust.ai/<snippet_id>/<view_type>?<optional_parameter>

Let’s break down each part:

​
Base Platform URL
string (constant)

https://app.trycrust.ai/ - This is the standard starting point for accessing any snippet viewer on the Crust AI platform.

​
Snippet ID
string (unique ID)

<snippet_id> - A unique string automatically generated by Crust AI when you create a snippet. It identifies which specific snippet configuration (linked table, design, filters, permissions, etc.) should be loaded. You’ll see this ID as part of the URL generated in Step 4 of the builder.

​
View Type
'detail' | 'list'

<view_type> - Specifies the initial view mode for the snippet:

  • detail: Loads the Detail View. Always used for Single Item snippets and when navigating to a specific record’s detail view within a Multiple Items Snippet.
  • list: Loads the List View. Only applicable to Multiple Items snippets.
​
Optional URL Parameter
?rec=<record_id> | ?p=<permission_value>

?<optional_parameter> - An optional key-value pair providing additional context. See details below.

​
Key URL Parameters Explained

These optional parameters are added after the ? and provide critical context, especially for targeting specific data or users.

​
Record Parameter (rec)
string (Airtable Record ID)

Format: ?rec=recXXXXXXXXXXXXXX

Purpose: Specifies the exact Airtable record whose details should be displayed.

When Used: Mandatory whenever the View Type is detail. It tells Crust AI which specific record’s data to fetch and render in the Detail View.

Applies To:

  • Single Item Snippets: Defines the only record this snippet URL will ever show.
  • Multiple Items Snippets (Detail View): Used internally when navigating from the List View to a specific item’s Detail View (/detail?rec=<clicked_record_id>).
​
Permission Parameter (p)
string (User Identifier)

Format: ?p=value (e.g., ?p=jamie@example.com or ?p=recABCXYZ)

Purpose: Provides the viewer’s unique identifier when User-based Permission is enabled for a Multiple Items Snippet.

When Used: Optional, but only relevant when the View Type is list and “User-based permission” is configured in Step 2.

Applies To:

  • Multiple Items Snippets (List View with User-based Permission): Tells Crust AI how to dynamically filter the list based on the viewer’s identity. If omitted, the user may be prompted for their identifier.

​
How Permissions Affect the URL and Viewer Experience (/list view)

Understanding the interplay between User-based Permissions and the p parameter is vital:

​
Scenario 1: User-based Permission ON, p Parameter MISSING

URL Example
https://app.trycrust.ai/<snippet_id>/list
URL Example
https://app.trycrust.ai/<snippet_id>/list?p=jamie@example.com

​
Scenario 3: “Anyone with the link” Permission ON

URL Example
https://app.trycrust.ai/<snippet_id>/list

​
Why is this Structure Important?

Key Benefits

  • Targeted Sharing: Allows you to create URLs that point to specific records (using rec) or filtered views for specific users (using p).
  • Automation: You can programmatically generate these URLs in Airtable (using formulas and RECORD_ID() or user identifier fields) or in tools like Make/Zapier to send personalized links automatically.
  • Navigation: When building multi-snippet applications, understanding how to pass the correct rec or p parameter from one snippet’s button to the URL of the next snippet is essential for creating seamless user flows.

Mastering the structure of Crust AI’s Shareable URLs unlocks the platform’s full potential for creating dynamic, secure, and integrated data applications based on your Airtable setup.