Send to Minuet takes a selection of companies and contacts from a FirstIgnite project and adds them to Minuet in one reviewed pass. It creates what's missing, links what's already there, and shows you the whole plan first.

Before you start: your Minuet connection must be active, and a team owner or admin must have enabled Send organizations & contacts in FirstIgnite, under Minuet Settings (app.firstignite.com/inteum/settings). Without it the button is visible but locked.

Prefer to watch first? Here's a one-minute walkthrough of Send to Minuet.

A project's Companies tab with thirty companies selected and the Send to Minuet button in the toolbar

The People tab toolbar after Select all, reading All 95 contacts across all pages are selected

Starting from companies, you can also tick Also send their Top People. That means the Top People whose employer is one of the companies you selected, not every contact at those companies. FirstIgnite writes companies first so each person attaches to the right one.

The Send to Minuet launch step: companies selected, Top People included, the Also send their Top People checkbox, and the note that nothing is written yet

The Companies and People tabs are separate lists, not filtered views of each other. The People tab is its own top-people list drawn from all the companies in the project. Selecting companies on one tab and then switching to the other will not give you those companies' people. If you want the contacts at particular companies, open the company, use its People tab, select the people there, save them to a custom list, and send from that list.

There's a limit of 200 records per send. Select more and FirstIgnite tells you, then takes the first 200. Companies come first, so nobody is sent ahead of their employer. Send the rest as a second batch.

FirstIgnite checks your selection against Minuet first. This step only reads. Nothing in Minuet changes until you confirm. You'll see the count as it works, and it gives up after two minutes, moving anything still unresolved into "We couldn't check these".

The reconciling step, counting through the selected records against Minuet

FirstIgnite groups the results:

The review step with three groups: Needs your decision, Will be created, Auto-matched (strong). The fourth group only appears when a check didn't come back

FirstIgnite excludes "We couldn't check these" on purpose. It couldn't confirm whether those records already exist, and Minuet's API has no delete, so a duplicate created by guessing would be permanent. Tick a row to send it anyway, or close and try again.

If the same rows come back unchecked on a second attempt, it isn't a slow response. Have your Minuet administrator check the API user's permissions on contacts and companies. An endpoint can be granted in the Endpoint Access Group and still be refused at the record level, and that refusal surfaces here as an unchecked row. See Troubleshooting the Minuet integration.

You may also see that some contacts will be sent without a company. Their employer isn't in this project, so there's nothing to link them to. Add the company to the project and send it too, or set the employer in Minuet afterwards.

Contacts without an email. If some contacts don't have an email yet, the review step offers Reveal X emails before sending, with the credit cost shown. It's unchecked by default. Leave it unchecked and those contacts are added to Minuet without an email. Tick it to reveal and include their emails, using one email credit each.

For anything under Needs your decision:

FirstIgnite tags decided rows Linked, Will create new or Skipped, and you can undo any of them. The summary at the top updates as you go: "{n} to create · {n} to link · {n} skipped".

Confirm when the plan looks right. FirstIgnite writes companies first, then people.

Failures don't roll back. If a record fails, everything already written stays written. The results screen lists what was created, linked, skipped, sent without a company, and failed, and offers Retry failed.

Sending twice is safe, with one exception. Reloading or clicking again won't duplicate a send in progress; FirstIgnite reattaches to the run rather than starting a second one. And because every send reconciles first, running the same selection again links to what's already there instead of creating it twice. The exception is overriding a row FirstIgnite auto-matched and telling it to create instead. That creates a second record, permanently.

After about twenty seconds without progress FirstIgnite tells you it's taking longer than usual. The records may still be going through, and closing the window doesn't cancel them. Check the results later.

You don't need the bulk flow for a single record. Open the person or company, use the Minuet badge, and create or link there. Same permission, same matching. See Matching and adding contacts and companies in Minuet CRM.

If something isn't working, see Troubleshooting the Minuet integration.