100Bug icon

100Bug

Usar a API privada do CRM 100Bug em workflows do n8n

Fila → Criar

AI-generated

Summary

Create a 100Bug lead distribution queue by sending its scope, name, funnel and phase, and configured distribution options to the CRM. The node returns the API response for the created queue.

Inputs

  • Escopo — Queue scope: Corretor, Equipe, or Imobiliária; defaults to Imobiliária.
  • Nome (required) — Queue name; the node trims whitespace and rejects an empty value.
  • Ativo — Whether the queue is active; defaults to true.
  • Funil (required) — Select a funnel from the searchable list or provide its numeric ID.
  • Fase (required) — Select a phase from the list for the chosen funnel or provide its numeric ID.
  • Tipo De Distribuição — Choose Aceite or Automático; defaults to Automático.
  • Tipo De Atribuição — Choose Adicionar or Substituir; defaults to Substituir.
  • Aceita Tudo — Whether the queue accepts all leads; defaults to false.
  • Tempo De Aceite (Minutos) — Lead acceptance time in minutes; defaults to 5.
  • Hora Início and Hora Fim — Optional start and end times, such as 08:00 and 18:00. Empty values are omitted.
  • Redistribuição Em Lote — Whether batch redistribution is enabled; defaults to true.
  • ID Da Equipe — Team ID; the UI says this is required for Equipe scope and that 0 omits it. The node sends a positive numeric ID or null.
  • Canais — Optional channel IDs selected from the list or supplied as expressions; sent as channel ID objects.
  • Corretores — Optional broker entries with broker ID, current weight, original weight, and position. The node sends these as a broker list.
  • Regras — Optional rules with active flag, condition, and value; the available condition is Contenha.
  • Campos Adicionais (JSON) — Optional JSON object merged into the create request body; it can add or override fields built from the other inputs.

Output shape

The API response for the created queue, emitted as n8n item data.

If the response is an object, it becomes one output item; if it is an array, each entry becomes a separate item. A non-object response is wrapped as {"data": value}. Output items retain their pairing with the corresponding input item.

Links

Discussion