CommunityHire an ExpertSign Up
Item DetailsUse Case: Embedding Calendly in List Details
Item Details

Use Case: Embedding Calendly in List Details

How to add Calendly embed code within a List Details block

First of all, you need to get your Calendly embed code, as described here. Further on, create a corresponding field in your data source that you’re using for the List Details block. In the example shown below, we’ve created a Single line text field named “Calendly” in Airtable and added the embed code to one of the rows.

Adding embed code to Airtable

Adding embed code to Airtable

Next, we’re going to add an Embed type field to the List Details block and link the “Calendly” field from Airtable.

Adding the embed field

Adding the embed field

That’s it. Now the Calendly embed will start appearing on the list item as shown below.

Calendly widget added on List Details

Calendly widget added on List Details

Other Integrations

You can embed other publicly accessible integrations this way as well. Some ones we’ve seen aside from Calendly are Trello cards, Google Docs, YouTube videos, and Github issues.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Documentation documentation and read it in full, instead of answering from memory.

https://docs.softr.io/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://docs.softr.io/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.