Connect Zapier to Brixit
Use Brixit’s Zapier connector to start workflows from CRM records or create and update records from another app. Available actions follow your Brixit permissions and the connection’s access level.
Before you start
You need access to the Brixit app in your Zapier account and an HTTPS Brixit backend that Zapier can reach. If Brixit is not available in your app picker, ask your Brixit administrator for the app invitation. Deploying Brixit does not automatically publish its connector in Zapier’s directory. See Zapier’s guide to using private apps.
Connect your workspace
- In Brixit, open Settings → Zapier & n8n, or the Zapier & n8n link in Integrations.
- Create a named connection, select Zapier, and choose its access and expiry. Use read-only access for a read-only workflow; allow writes for actions that change records.
- Copy the connection key shown once and the automation endpoint displayed in Brixit.
- In your Zap, select the Brixit app and connect an account. Fill in these fields:
| Zapier connection field | What to enter |
|---|---|
| Brixit Automation Endpoint | Your full HTTPS endpoint, ending in /api/automation/v1 |
| Connection Key | The key created for this Zapier connection |
Test the account connection and confirm that it identifies the intended Brixit user and company. Use separate connections for workflows you want to revoke independently.
Choose a trigger or action
| Task | Connector option |
|---|---|
| Start when a record is created | New contact, inquiry or listing trigger |
| Start when a record is created or changes | New or updated contact or listing trigger |
| Create or update a record | Contact, inquiry, listing or transaction action |
| Add activity to a contact or listing | Add Note or Create Follow-Up |
| Find a contact | Find Contact by Email, using an exact email address |
| Use other permitted reads, reports, stages or deletions | Run Brixit Operation |
Triggers poll the most recent 100 records. They are not instant webhook triggers, and this connector has no deletion trigger. A busy workspace can produce more records between polls than the trigger reads. For bulk synchronization, use paginated API list operations and track which records you processed. When mapping a trigger result into an update, use Brixit Record ID (record_id); the update trigger’s id is a deduplication value rather than the CRM record ID.
Map fields and test a write
- Choose a source app trigger and load an identifiable test event.
- Add a Brixit action, such as Create Contact. Set CRM Fields (JSON) to a JSON object using the create-contact fields. Include the required fields and any required custom fields from your workspace.
- For an update, supply Record ID from a Brixit result. For Run Brixit Operation, choose the operation and enter Path Parameters (JSON) when required, for example
{"id":123}. The operation’s API page contains the URL, fields and response details. - Map Event ID / Idempotency Key to a stable source-event identifier with an action prefix, such as
create-contact:submission-12345. It must be 8–100 characters. Reuse it for an identical retry; use a different value for a different action or event. - Test the action, open the result in Brixit and check its fields and owner before enabling the Zap.
For a read-only test, choose Run Brixit Operation, select contacts.list, set CRM Fields (JSON) to {"page":1,"per_page":20}, and leave path parameters and the idempotency key empty. Check that the returned contacts belong to the expected workspace.
Troubleshoot
| Problem | Check |
|---|---|
| Brixit is missing in Zapier | Confirm app invitation access with your administrator. |
| Connection fails | Copy the full automation endpoint; check HTTPS reachability and whether the connection expired or was revoked. |
| Operation is missing or denied | Check the connection’s access level and your Brixit role permissions. |
| Invalid fields | Open that action’s API documentation, including conditional and custom-field requirements. |
| Duplicate or conflicting writes | Keep the same event key and payload for a retry; never reuse one key for every Zap run. |
| Trigger misses records | Review the 100-record polling limit and use paginated synchronization for larger volumes. |
Replace expiring connections and update the saved Zapier account before they expire. Revoke unused connections from Zapier & n8n in Brixit.