Remarcable Integration - EVOLVE Electrical

1. Overview

The eVolve Remarcable Integration is an eVolve Electrical add-in for Autodesk Revit that lets you push project material data — bills of material (BOM), wire/conductor takeoffs, and prefab assemblies — from your Revit model directly into a linked Remarcable project. Instead of exporting spreadsheets and re-importing them by hand, you select the items you want, choose a Remarcable list, and send them in a single step.

What it does:

  • Links a Revit model to a specific Remarcable project (job).
  • Reads material data from your eVolve Data Profiles and Data Tables.
  • Lets you preview, filter, group, and select items across three categories — BOM, Wire, and Prefab.
  • Sends the selected items into a named Remarcable list (and optional sublist).
  • Optionally exports the same data to a CSV file instead of sending it, so you can review before going live.

What you need before you start:

  • Autodesk Revit (2024, 2025, 2026, or 2027) with eVolve Electrical installed and loaded.
  • A Remarcable account with access to the project (job) you want to sync to, including your Remarcable sign-in email and password.
  • One or more eVolve Data Profiles configured for the integration (your eVolve administrator typically sets these up — see Section 3).

Note: The integration works with electrical model content. The data it collects comes from electrical categories such as conduit, conduit fittings, cable tray and fittings. Materials that are mapped is still work in progress, so some items will come in as "customs".

2. Finding the Integration in Revit

After eVolve Electrical loads, the Remarcable tools appear on the eVolve Integrations ribbon panel as a Remarcable split button with three commands:

Button

What it does

About

Shows version information for the integration and the host Revit and eVolve Electrical versions.

Login

Opens the Remarcable Login and Project Mapping window — used for authentication, connection settings, and linking this Revit model to a Remarcable project.

Send BOM

Opens the Remarcable Send BOM window — the main workspace where you review and send BOM, Wire, and Prefab data.

A typical first-time flow is: Login (authenticate + map the project) → Send BOM (review and send data).

3. Setup

Setup is a one-time task per Revit model (plus occasional updates if your credentials or project mapping change). It has three parts: signing in, mapping the project, and — only if needed — adjusting connection settings.

3.1 Sign in and map the project

  1. Open the Revit model you want to sync.
  2. On the ribbon, click Remarcable ▸ Login. The Remarcable Login and Project Mapping window opens.
  3. Fill in the fields:

    Field

    Description

    Revit Project

    Read-only. Shows the current Revit model name for reference.

    Remarcable Email

    Your Remarcable account sign-in email.

    Remarcable Password

    Your Remarcable account password. (Masked.)

    Remarcable Project

    The Remarcable project (job) to link this model to. Use Load to populate the list.

  4. Click Test Login to confirm your email and password are valid. On success you'll see "Login succeeded. Auth email and password are valid."
  5. Click Load to retrieve your active Remarcable projects. Select the correct project from the Remarcable Project drop-down. (If you have logged in before, the integration will try to load and pre-select your projects automatically when the window opens.)
  6. Click Save.

This stores two things:

  • Your credentials and connection settings are saved to your personal settings on this computer (they are not stored in the Revit model and are not shared with other users).
  • The project link (project name and job number) is saved inside the Revit model, so anyone who opens the model and has their own Remarcable credentials can send to the same project.

If you try to change a model that is already linked to a different project, the integration asks you to confirm the change before saving.

Multiple users, same project: If more than one person sends BOM, Wire, or Prefab data from different sessions of the same (or different) Revit models into the same Remarcable list, each send is processed independently — the integration does not detect or merge duplicate items across sessions. If your team has more than one person syncing the same model or project, coordinate who sends and when to avoid duplicate entries in Remarcable.

3.2 Connection settings (advanced)

Most users never need to change these. The endpoints are pre-filled with Remarcable's standard production addresses. To view or change them, click the gear icon in the top-right of the Login window to open Connection Settings:

Field

Default

Purpose

Token Endpoint

https://app.remarcable.com/api/v1/auth/token/

Where the integration exchanges your email/password for a secure access token.

Project List Endpoint

https://app.remarcable.com/buyer_api/v1/ListProject/

Where the integration retrieves your list of Remarcable projects.

API Token (optional override)

(blank)

An optional pre-issued API token, used instead of email/password. Most users should leave this blank. If your organization uses a shared service account for Remarcable syncs, ask your eVolve administrator for a token to enter here.

Buttons:

  • Restore — resets the Token Endpoint and Project List Endpoint back to their default Remarcable values (useful if a field was edited by mistake).
  • OK — keeps your changes for this session.
  • Cancel — discards changes.

How authentication works: When you send data, the integration signs in with your email and password to obtain a short-lived access token, which it caches for the working session (about 8 hours) and refreshes automatically if it expires. If you supplied an API token override, that token is used directly. If a send fails because the token expired, the integration refreshes it and retries the send once automatically. If that retry also fails, you'll see a standard send error — re-check your credentials and project/list access via Login, and try sending again.

4. The Send BOM Window

Click Remarcable ▸ Send BOM to open the main workspace, titled Remarcable Send BOM.

4.1 Common elements

  • Remarcable Project (top of window) — confirms which Remarcable project this model is linked to, shown as {job number} | {project name}. If you see "No Remarcable project linked to this Revit model," return to Login and map the project first (Section 3.1).
  • Gear icon (top-right) — opens the eVolve Data Profiles configuration.
  • Help icon (?) (top-right) — opens the Remarcable website for help.
  • Four tabs: BOM, Wire, Prefab, Options.
  • OK — saves your option selections (such as the wire source table) to the model and closes the window.
  • Close — closes the window without sending.

4.2 Working with the grids

All three data tabs (BOM, Wire, Prefab) share the same grid behavior:

  • Select items using the checkboxes in the first column. A header checkbox selects or clears all rows. Only checked rows are sent.
  • Group rows by dragging a column header into the bar labeled "Drag a column header here to group by that column."
  • Filter and sort by clicking column headers.
  • Grids are read-only — you cannot add or delete rows here; the data reflects your model and selected profiles.

5. Processing and Sending a BOM

5.1 BOM tab

The BOM tab shows bill-of-material items sourced from your selected eVolve BOM Data Profiles.

  • Display By drop-down — choose Current View (default) or Current Project to control the scope of items shown.
  • Columns: ElementId, Description, Length, Quantity, and (when present in the data) UOM, Spool Name, Category, Subcategory, and Comments.
  • Aggregate List checkbox (bottom-left) — when checked, rows that share the same Description and UOM are combined on screen for display: Length and Quantity are summed, and any differing descriptive values show "varies." This only changes what you see in the grid before sending — it does not change what gets sent. Unchecking it (or reopening the window) restores the ungrouped view; nothing about your underlying model data is altered.
  • Send BOM button (bottom-right) — starts the send workflow (Section 8).

Note on send-time grouping: Regardless of whether Aggregate List is checked, the actual send (Section 8.4) always groups checked items by description and unit before transmitting — lengths are summed for linear items and quantities are summed for each-based items. Aggregate List simply lets you preview that grouping ahead of time; it does not add an extra grouping step of its own.

5.2 Wire tab

The Wire tab shows conductor/wire run data sourced from an eVolve data table (by default, the Conduit Run Schedule).

  • Run ID filter — a multi-select drop-down listing every Run ID in the data. A Run ID identifies a single continuous wire run between two points in your model (for example, from a panel to a device). Check the runs you want to see; use Select All to toggle everything. The grid filters as you change the selection.
  • Columns: ID, Description (a readable wire description built from size, material, insulation, and color — e.g. "12AWG Stranded 1/C CU THHN, PVC-Nylon, Black, 600V"), Length, Run Id, Start, Finish, and Status.
  • Source Data notice (bottom-center) — shows where the wire data came from and when it was last refreshed:
    Source Data Last Updated: 5/1/2026 3:32 PM
    Source Data Table: Conduit Run Schedule
    A dash (-) means the timestamp or table is unavailable.
  • Send Wire button — starts the send workflow (Section 8).

How wire is summarized and colored is controlled on the Options tab (Section 7). Unlike the BOM tab's Aggregate List checkbox, the Wire Aggregation Options on the Options tab control the actual grouping of wire data shown in this grid and sent to Remarcable — see Section 7.2.

5.3 Prefab tab

The Prefab tab shows prefab/assembly items sourced from your selected eVolve Prefab Data Profiles.

  • Display By drop-down — Current View (default) or Current Project.
  • Columns: ID, Description, Quantity, Category.
  • Send Prefab button — starts the send workflow (Section 8).

6. Choosing Data Profiles

The BOM and Prefab tabs are populated from eVolve Data Profiles — reusable definitions that map your Revit parameters to the fields the integration sends. You choose which profiles feed each grid on the Options tab:

  • BOM Data Profiles"Select one or more data profiles used to source the BOM table."
  • Prefab Data Profiles"Select one or more data profiles used to source the Prefab table."

Check one or more profiles in each list; the corresponding grid reloads automatically. You can combine several profiles at once, and duplicate items are removed.

If a grid is empty, it usually means no matching Data Profile is selected (or none exists yet). Use the gear icon at the top of the window to open the eVolve Data Profiles configuration, or contact your eVolve administrator.

7. Options Tab

The Options tab controls how data is sourced, summarized, and delivered.

7.1 Data Profiles

The BOM Data Profiles and Prefab Data Profiles checked lists (described in Section 6).

7.2 Wire Options

  • Select Wire Source — the eVolve data table that supplies wire data (default Conduit Run Schedule). Your choice is saved to the model. The Data Tables button opens the eVolve Data Tables configuration to define or edit tables.
  • Select Circuit Color Source — the data table used to resolve conductor colors (default Circuit Colors).
  • Wire Color Options — controls how conductor color appears in the wire description:
    • Use all colored conductors (default)
    • Use all black conductors
    • Use black conductors for sizes larger than [size] (default threshold 4)
  • Wire Aggregation Options — controls how wire rows are combined, both in the grid and in what gets sent:
    • Sum by wire type (description) (default) — identical descriptions are merged and their lengths summed.
    • Itemize by Run Id — each run is listed separately, no merging.

Changing any wire option reloads the Wire grid immediately and is saved to the model.

7.3 Export to CSV only

  • Export to CSV only (does not send to Remarcable) checkbox — "When enabled data will not be sent to Remarcable but will only export data to .csv to the desktop."

Use this to validate your data before sending it live. When enabled, the send workflow performs all the same validation but writes a CSV file to your Desktop instead of transmitting anything to Remarcable.

You'll still be asked to choose or name a target Remarcable list and sublist (Section 8.2) even in CSV-only mode. This list name is used only to confirm what you would send to in the on-screen summary — it is not written into the CSV file or its filename, and no connection to Remarcable is made.

8. The Send Workflow

This is the same for Send BOM, Send Wire, and Send Prefab.

8.1 Before you send (preconditions)

The integration checks that:

  1. A Remarcable project is linked to the model. (If not: "No Remarcable project is linked to this Revit model. Use the Login button to select a project first.")
  2. Authentication is configured — credentials or an API token. (If not: use Login to enter them.)
  3. At least one item is selected (checked) in the grid. (If not: "Select at least one item in the … grid before running sync.")
  4. For BOM/Prefab, at least one Data Profile is selected.

8.2 Choose the target list

After clicking a send button, the Select Remarcable List window appears:

  • Pick an existing Remarcable list from the drop-down, or type a new list name. The default suggestion is eVolve Sync.
  • Sublist (BOM and Wire only) — optional. When provided, the items go into this sublist under the chosen list.
  • Click OK to proceed, or Cancel to stop.

If existing lists can't be loaded automatically, you can simply type the list name to use.

8.3 Confirm (CSV-only mode)

If Export to CSV only is enabled, a confirmation appears summarizing the target list and item count and asks you to continue with CSV export only. Click Yes to proceed or No to cancel.

8.4 Sending

During a live send, the window shows a wait cursor and is temporarily disabled while items are transmitted to Remarcable. Checked items are grouped by description (and unit) before sending: for linear items (feet) the lengths are summed, and for each-based items the quantities are summed.

Items that fail validation (Section 9) are skipped and reported individually in the error summary — they do not block the rest of the batch from sending.

8.5 Results

When finished, a summary dialog reports the outcome — the target list, total items, the number that succeeded, and the number of errors. For CSV-only runs, it confirms that nothing was sent and reports the validated item count.

  • CSV files are written to your Desktop with a timestamped name such as RemarcableSyncCsvExportOnly_2026-06-30_15-42-08.csv, and the window confirms the full path. The export includes: ElementId, UniqueId, Description, Category, Subcategory, Quantity, Length, Unit, SpoolName, and Comments.
  • If there were errors, you're asked whether to "Review detailed sync errors?" Choosing Yes opens a Sync Errors window listing each issue with its Element ID, field, source, a plain-language reason, a suggested action, and an error code. You can Copy or Export CSV from this window to share with your team or eVolve support.

9. What Makes an Item Valid

For an item to send successfully, the data mapped through your Data Profile must include:

  • Description — required.
  • Quantity — required, and greater than zero.
  • Category — required.
  • Length — required for linear units (feet), and greater than zero. Not required for each-based (EA) items.
  • UnitEA (each) or FT (feet).

Items missing required values are not sent and do not stop the rest of the batch — they're reported individually in the error summary (Section 8.5) with guidance on what to fix, typically updating the Data Profile mapping or populating the source parameter on the element. Every other valid, checked item in the same send still goes through.

10. Troubleshooting

Symptom

Likely cause & fix

"No Remarcable project linked to this Revit model."

The model hasn't been mapped. Run Login and map the project (Section 3.1).

"No Remarcable authentication is configured."

No credentials saved. Run Login, enter email/password (or an API token), and Test Login.

Project list is empty after Load

Verify your Remarcable account has access to active projects, and that the Project List Endpoint is correct (Section 3.2).

A grid is empty

No matching Data Profile is selected on the Options tab, or none exists. Select profiles or configure them via the gear icon.

Send fails with an HTTP/authorization error

Confirm your credentials are current and your account has access to the chosen project and list. The integration automatically retries once after refreshing an expired token; if it still fails, re-enter your credentials via Login and try again.

Wire descriptions show the wrong colors

Check Wire Color Options and the Select Circuit Color Source table on the Options tab.

Some items didn't send, but others did

This is expected — items that fail validation (Section 9) are skipped individually and reported in the error summary, while valid items in the same batch still send.

Getting help from eVolve support. If you need to contact eVolve support about a sync issue, they may ask for your diagnostic log, found at:

%APPDATA%\eVolve\Remarcable Integration\Logs\RemarcableApiDiagnostics.log

11. Quick Reference

First-time setup

  1. Remarcable ▸ Login → enter email & password → Test Login.
  2. Load → select your Remarcable project → Save.

Sending a BOM

  1. Remarcable ▸ Send BOM.
  2. On Options, select your BOM/Prefab Data Profiles and wire settings. Optionally check Export to CSV only if you want to validate your data before sending it live.
  3. On the BOM, Wire, or Prefab tab, check the items to send.
  4. Click Send BOM / Send Wire / Send Prefab.
  5. Choose (or name) the target Remarcable list and optional sublist → OK.
    • If CSV-only is enabled, confirm the export when prompted; a CSV file is written to your Desktop.
  6. Review the completion summary; open the error report if prompted.


How did we do?

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)