Build and upload a canvas

Before you begin

Connect the Salesforce org where you want to work. Org Loom uses your Salesforce user's object, field, record, and sharing access, so the objects and fields available to you may differ from those available to another user.

In a Team workspace, a workspace admin grants the permissions for the actions you use. Completing this walkthrough requires Upload to Salesforce; loading or saving records may also require Browse records, Import via SOQL, or Save canvases.

Cards on the canvas use three useful states:

• Draft: a new record that does not yet exist in Salesforce.
• Existing: a Salesforce record loaded without local changes.
• Modified: an existing record with changes staged on the canvas.

The process

1. Add new drafts or load existing Salesforce records.
2. Edit records and connect related cards.
3. Optionally save the canvas so you can return to it later.
4. Open Upload to Salesforce and review the checks.
5. Confirm the upload, then review the result.

Step 1: Add records

On an empty canvas, Start building your canvas offers the most common starting points:

• Browse records finds existing records with point-and-click filters.
• Add a blank record creates a new draft for the object you choose.
• Import CSV stages rows from one or more files.
• Import via SOQL loads the results of a Salesforce query.
• Generate with AI proposes new draft records from a description.

Add a blank record lists only object types that the connected Salesforce user can create.

After records have been added, use + Add records in the canvas toolbar to add more. You can also right-click an empty part of the canvas and choose Add record here.

Step 2: Edit and connect records

Double-click a card, or open its menu and select Edit, to change field values. Saving the editor updates only the canvas. Existing records receive a modified badge when their staged values differ from Salesforce.

To represent a lookup or master-detail relationship, drag a link between the related cards. If more than one Salesforce relationship could connect them, Org Loom asks which field to use. Keeping both the parent and child on the canvas lets Org Loom create new parents before their children and fill the relationship during upload.

Use the record counter above the canvas to check how many records are drafts, modified, or unchanged before you continue.

Step 3: Save the canvas, if needed

Open the menu beside Save canvas and choose Save as new canvas the first time. When you own an open saved canvas, Save changes updates it. Saved canvases remain in your Salesforce org so you can reopen or share them later.

Saving preserves the canvas layout and staged work. It does not create or update the Salesforce business records shown on the canvas, and it is not required before an upload.

Step 4: Review the upload

Select Upload to Salesforce. Org Loom checks the records and shows any missing required values, incompatible values, validation problems, or relationship issues it can identify before the upload.

• Drafts are prepared as new Salesforce records.
• Modified cards are prepared as updates.
• Unchanged existing records are skipped.
• Records marked for deletion are handled after creates and updates.

If you upload only a selection, Org Loom includes only the selected records. A required relationship to an unselected draft blocks the upload until you select that related draft too. An optional relationship to an unselected draft is left out and called out in the review.

Step 5: Upload and review the result

Choose Upload when the review is correct. Salesforce still applies the connected user's permissions, validation rules, duplicate rules, flows, triggers, and other automation while the records are written.

The result shows which records succeeded and which failed. Successful drafts become existing cards with Salesforce record IDs. Correct any failed rows on the canvas, then upload those records again.

Keep the result until you have reviewed it. If a completed upload needs to be undone later, open Upload history and use Recall where it is available.

Important limits

• A canvas can contain up to 500 record cards.
• Pre-flight checks catch many common problems, but Salesforce remains the final authority and may reject a record during the upload.
• An interrupted upload can produce a mix of successes and failures. Review the result before retrying.

See also

• Editing existing records
• Saving canvases
• Importing CSV files onto the canvas
• Recalling a Salesforce upload