Bring public data into Framer.

Choose the result you need.

The plugin runs in the Framer editor. CMS imports copy selected fields into your project. The Request Console is a separate component that can read public data after the plugin is closed.

1. Open ErinTech Connect on the Framer Marketplace, choose Open Plugin and select your project. Start in an unpublished copy while learning the workflow.
2. For articles or structured content, start with Included example or ErinTech demo API — CMS content, then choose CMS import.
3. For the interactive request viewer, choose ErinTech demo API — requests, then Request console. Open the plugin from the canvas to insert components.
4. For your own data, choose Public API and enter an HTTPS URL with browser CORS access. Do not include credentials, API keys or private data.

Sync is manual. This plugin does not host an API, query a private database, schedule imports or provide authentication. The template works with sample data without the plugin.

• Open ErinTech Connect · Free plugin

Import your first three draft items.

Use the included example to learn the workflow before connecting your own feed.

1. Select Included example → Load source → CMS import. Keep Records path /items, Stable ID path /id and the suggested mappings. Name the collection.
2. Choose Review import. Open Preview mapped values and inspect the per-ID actions. This step does not write content.
3. Choose Apply 3 changes. Open Framer CMS and inspect the three draft records. Bind the collection to your intended page layout and review it before publishing.
4. For the next sync, reload the same source, choose Find existing connections and select that collection. Review again: unchanged data should propose zero changes.

Use a new collection to change a connection’s source URL or mapping. Up to eight text, number or boolean mappings, 100 source records per import and 500 destination items are supported.

Keep manual edits visible.

Imports match records by their stable external ID. Manual changes to mapped fields appear as conflicts and are skipped. Unmapped fields are preserved; source-absent items are never automatically deleted.

1. Keep External ID unchanged. Do not remove mapped fields or change their types. Display names may be renamed because mappings track field identity.
2. If you see a conflict, compare the source and destination and decide where the final value belongs. No force-overwrite action is provided.
3. If an import is interrupted, keep completed records, reload the same source and review the destination again before retrying. Do not assume a failed batch rolled back.

Connect the request viewer.

Load ErinTech demo API — requests and choose Request console. The hosted demo contains six simulated records over a real HTTPS connection; it is a fixed snapshot, not live customer activity.

1. Choose Insert console and place the component in a responsive stack. Open Preview and check search, status filters, sorting and record details.
2. To update an existing compatible console, select it on the canvas, choose Inspect selected console and review its name. Configure selected console changes only its data source and URL; visual settings are preserved.
3. Use Included example for a console with local sample requests. For a real feed, select Public API and load a response matching the version 1 format linked below.
4. Test Preview and the final published domain. Editor access does not establish that your public domain has the required CORS permission.

The feed accepts at most 100 requests with unique IDs. Each record needs id, workflow, model, status, durationMs, costUsd, tokens, startedAt and summary. Status is completed, retried or error; metrics are non-negative, finite numbers and timestamps are UTC ISO dates. An empty requests array is valid. Responses are limited to 200,000 characters, with a ten-second timeout and manual Refresh.

• View the version 1 request example ↗

Find the next useful step.

Use these checks before asking for support. Keep credentials and private records out of screenshots and reports.

Know where your data goes.

The plugin sends feed requests directly from your browser to the chosen endpoint without credentials. It has no analytics, advertising or ErinTech data-upload endpoint.

1. Mapped CMS values are written to your Framer project. Connection metadata stores the source URL, field mapping and SHA-256 comparison baselines. Those baselines are not an encryption or secrecy feature.
2. An inserted public console stores its feed URL in the project and reads it from each visitor’s browser. Anyone can inspect the response. Use only data intended for publication.
3. The feed host and Framer process the requests needed to operate their services. Loading ErinTech’s demo feeds contacts our hosting; ordinary hosting access logs may include request metadata. This guide and plugin add no analytics or tracking cookies.
4. To disconnect, stop imports and remove or reconfigure the console. Already imported items and connection metadata remain in Framer until you remove the relevant collection using Framer’s controls.

The launch checklist on this guide stores no data: ticks exist only in the current page session and reset on reload. Contacting support uses the separate company website and its privacy information.