Skip to content
Brixit

Connect n8n to Brixit

Use n8n’s built-in HTTP Request node to read and manage Brixit contacts, inquiries, listings, transactions, notes and follow-ups, or retrieve reports. Available actions depend on your CRM permissions and the connection’s access level. No community node installation is required.

Create a Brixit connection

  1. Open Settings → Zapier & n8n, or the Zapier & n8n link in Integrations.
  2. Name the connection, select n8n and choose its access level and expiry. Start with Read only while checking the connection.
  3. Create the connection and copy the key shown once into n8n’s credential store.
  4. Copy the automation endpoint displayed in Brixit. It ends in /api/automation/v1.

Create a separate connection for each workflow you want to revoke independently. Zapier and n8n use the same Brixit endpoint and connection-key approach.

Test the connection in n8n

  1. Create a workflow with a manual trigger and an HTTP Request node.
  2. Set the method to GET and append /me to your Brixit automation endpoint.
  3. Set Authentication to Generic Credential Type, then choose Bearer Auth.
  4. Create a credential with your Brixit connection key as the Bearer Token.
  5. Execute the node and confirm that the returned user and company are correct.

Use your CRM’s HTTPS address, reachable from the n8n instance running the workflow. See n8n’s HTTP Request credential guide for its authentication settings.

For required fields, allowed values and live testing, open the Brixit API reference.

Run an operation

Use GET with /operations to see the actions available to your connection. To run one, use POST with /execute, keep the same Bearer Auth credential, and send a JSON body. For example, to read the first page of contacts:

{
  "operation": "contacts.list",
  "data": { "page": 1, "per_page": 20 }
}

Writes require a connection with the appropriate write or delete access and an idempotency_key of 8–100 characters. Give each source event and action a unique key, such as follow-up:inquiry-12345, and reuse it when retrying that same action. This prevents a successful write from being repeated after a retry.

Use a Schedule Trigger for scheduled reads or a trigger from another app to start your workflow. Handle pagination for larger lists and track processed records when syncing repeatedly. Test the result in Brixit before enabling the workflow.

Manage access and troubleshoot

  • Connection expired or revoked: create a replacement in Brixit and update the n8n credential.
  • Action unavailable: check both the connection’s access level and your CRM role.
  • Connection cannot load in Brixit: ask your administrator to confirm that the installation has the automation update and its database migrations, and that automations are enabled.
  • Too many requests: wait for the retry interval returned by Brixit before trying again.

Revoke a connection from Zapier & n8n when the workflow no longer needs access.