Skip to content
Start in the sandbox
All connectors
Lucid logo

Lucid

Content creation & media

Move briefs, assets and sign-offs through Lucid without chasing between tools.

13 ways to read, 5 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Lucid with Nexra

Connected, approved, proven.

The things teams do most with Lucid, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Create document from templatedocuments.createApproval by rule
  • Create folderfolders.createApproval by rule
  • List account usersaccount_users.listRead

Example flow

  1. Lucid · List account usersaccount_users.listDone
  2. Lucid · Create document from templatedocuments.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Lucid.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Lucid
  • Lucid's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Lucid REST API for Lucidchart, Lucidspark and Lucidscale: search and read documents and their contents, folders, collaborators, comment threads and users; copy templates, organise folders and comment.

Lucid Software Inc. API docs
Source actions
13
Destination actions
5
Data types
9

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

account users3
  • Get account userSource

    One user on the authorised account.

  • List account usersSource

    Users on the authorised account (account token or admin scope).

  • Find users by emailSource

    Users on the account whose email exactly matches (sent in the request body).

comment threads1
  • List comment threadsSource

    Comment threads on a document with status.

document collaborators1
  • List document collaboratorsSource

    Users with access to a document and their roles.

document pages1
  • List document pagesSource

    Pages of a Lucidchart or Lucidspark document with shape, line and group counts and their text.

documents5
  • Create document from templateDestinationNot retried automaticallyApproval before production

    Copy an existing document or template into a new document with a title, optionally in a folder.

  • Get documentSource

    Document metadata: title, product, links, version, pages, owner and attributes.

  • List documentsSourceIncremental

    Documents the user can read, oldest created first, with modified-time and product filters.

  • Search documentsSource

    Documents matching keywords, ranked by relevance.

  • Update documentDestinationProvider duplicate protectionApproval before production

    Rename a document, move it to another folder or repository, or set its tags.

folder contents1
  • List folder contentsSource

    Documents and sub-folders in a folder, or in the user's root folder.

folders3
  • Create folderDestinationNot retried automaticallyApproval before production

    Create a folder, optionally inside another folder.

  • Get folderSource

    Folder or team folder name, parent, repository and attributes.

  • Update folderDestinationProvider duplicate protectionApproval before production

    Rename a folder or move it under another folder.

thread comments2
  • Post thread commentDestinationNot retried automaticallyApproval before production

    Add a comment to an existing comment thread on a document.

  • List thread commentsSource

    Comments in a document's comment thread, with authors and assignees.

users1
  • Get authorised userSource

    The authorised user's profile: name, username, email and account.

Access and limits

Authentication
Lucid OAuth 2.0 client (user token with offline access; refresh tokens rotate)
Plans and access
Any Lucid account can create an OAuth 2.0 client in the Lucid developer portal. User and account management reads need an account (admin) token. User tokens act as the authorising user and see only documents and folders shared with them. Account-wide document search needs admin scopes.
Test environment
Lucid has no sandbox; authorise the OAuth client with a test Lucid account.
Rate limits
15 requests per second per user token and 50 per account token; document and folder search are limited to 300 requests per 5 seconds per account. HTTP 429 includes Retry-After in seconds.
Pagination
Paginated endpoints take pageSize (up to 200) and return a Link rel="next" URL with an opaque pageToken; Nexra follows it.
Provider events
Lucid does not offer webhooks on the REST API. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • No deletes or trashing: Nexra never trashes documents or folders, removes collaborators or deletes share links.
  • No sharing changes: Nexra does not create, update or accept share links, or add or change collaborators, so content is never made public.
  • Document creation copies an existing document or template (POST /documents/copy). Creating from Standard Import JSON or an external file needs a file upload and is an engine gap, as is image export of documents.
  • User list and lookup need an account token or admin scopes (account.user:readonly); a user token returns HTTP 403.
  • Lucid documents the token endpoint with a JSON body; Nexra sends the standard form-encoded refresh request, which Lucid accepts (it parses form fields), but this content type is not documented.
  • Document contents are summarised per page (shape, line and group counts and text); the full shape model is not mapped.
  • Comment threads and comments are not paginated by Lucid.

Developer reference

  1. Create the Lucid Software Inc. credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Lucid, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Lucid Software Inc. docsAPI referenceLucid Software Inc. docsAuthenticationLucid Software Inc. docsRate limits

Machine-readable detail: GET /api/public/connect/connectors/lucid and the Connections API.