ai-agents15

answers-history4

automations6

business-areas6

channels5

contacts7

customers9

dynamic-forms7

form-publications9

forms6

funnel-steps8

goals7

integrations4

invites3

project-funnels13

project-groups9

projects42

search-activities1

spreadsheet-operations7

squads9

step-assistants8

system3

tags5

user-alias4

users2

step-assistants

Execução

Listar execuções dos assistentes

Histórico de execuções de todos os assistentes de uma etapa, do mais recente para o mais antigo.

Cada registro traz o assistente, o projeto, a execução do agente de IA (com o texto devolvido e o modelo usado) e o desfecho de cada destino separadamente: a gravação como conteúdo do projeto e a gravação em campo de formulário têm campos próprios de status e de erro, porque uma pode dar certo e a outra falhar.

Aceita filtros e paginação por query params, consulte:

Os campos de paginação (current_page, per_page, total, ...) vêm na raiz da resposta, ao lado de data, e não dentro de meta como no restante da API.

get/api/management/steps/{step}/assistants/execution-logs

Query parameters

pagestring

Página desejada. Padrão 1.

perPagestring

Itens por página. Padrão 30, máximo 100.

filter[status]string

Situação da execução: pending, success ou error.

filter[step_assistant_id]string

ID (UUID) do assistente cujas execuções devem ser retornadas.

Response

Sucesso

current_pageinteger required

Página retornada.

first_page_urlstring

Endereço da primeira página.

frominteger

Posição do primeiro item da página no total.

last_pageinteger

Número da última página.

last_page_urlstring

Endereço da última página.

next_page_urlstring

Endereço da próxima página, ou null na última.

pathstring

Endereço base usado para montar os links.

per_pageinteger required

Itens por página.

prev_page_urlstring

Endereço da página anterior, ou null na primeira.

tointeger

Posição do último item da página no total.

totalinteger required

Total de itens encontrados.

Changes

Changed in 4 of the 98 revisions of this API.19611

Aug 24, 20263c590152d5b51964See the full diff
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ▲
  the // response's property type changed from no type to string for status
  response-property-type-changed
- ▲
  the // response's property type changed from no type to boolean for status
  response-property-type-changed
- ▲
  the // response's property type changed from no type to string for status
  response-property-type-changed
- ▲
  the response's property format changed from uri to no format for status
  response-property-type-changed
- ▲
  the response's property format changed from uri to no format for status
  response-property-type-changed
- ▲
  the // response's property type changed from no type to integer for status
  response-property-type-changed
- ▲
  the // response's property type changed from no type to string for status
  response-property-type-changed
- ▲
  the response's property type changed from no type to string for status
  response-property-type-changed
- ▲
  the response's property format changed from uri to no format for status
  response-property-type-changed
- ▲
  the response's property type changed from no type to string for status
  response-property-type-changed
- ●
  added the new completed enum value to the /// response property for the response status
  response-property-enum-value-added
- ●
  added the new error enum value to the // response property for the response status
  response-property-enum-value-added
- ●
  added the new failed enum value to the /// response property for the response status
  response-property-enum-value-added
- ●
  added the new pending enum value to the /// response property for the response status
  response-property-enum-value-added
- ●
  added the new pending enum value to the // response property for the response status
  response-property-enum-value-added
- ●
  added the new success enum value to the // response property for the response status
  response-property-enum-value-added
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
Aug 19, 2026063de6e2e93c2See the full diff
- ○
  api tag Execução added
  api-tag-added
- ○
  api tag execution-logs removed
  api-tag-removed
Aug 19, 202669f9300dc0451See the full diff
- ○
  added the media type application/json for the response with the status
  response-media-type-added
Aug 19, 20263227b85304ca4See the full diff
- ○
  added the new optional query request parameter filter[status]
  new-optional-request-parameter
- ○
  added the new optional query request parameter filter[step_assistant_id]
  new-optional-request-parameter
- ○
  added the new optional query request parameter page
  new-optional-request-parameter
- ○
  added the new optional query request parameter perPage
  new-optional-request-parameter

Full history