Skip to content
AdlyseDocs
Product guideMCP reference
⌘K
Open Adlyse
⌘K
Overview
QuickstartAuthentication
adlyse-insights
adlyse-ads
adlyse-workflows
list_workflowsget_workflowrun_workflowget_run_statusget_node_runget_workflow_schemacreate_workflowupdate_workflowdelete_workflowcreate_releaselist_releasesset_production_releasedelete_releaselist_authoring_resourceslist_tablesget_tablequery_table_rowscreate_tableadd_table_columnsadd_table_rowsupsert_table_rowsupdate_table_rowsdelete_table_rowsupdate_tabledelete_tableupdate_table_columndelete_table_columnreorder_table_columnslist_schedulesget_schedulecreate_scheduleupdate_schedulepause_scheduleresume_scheduledelete_scheduletrigger_schedulerun_assistantget_assistant_runlist_assistant_threadsget_assistant_threadlist_assistantsget_assistantcreate_assistantupdate_assistantdelete_assistantlist_assistant_handoffscreate_assistant_handoffupdate_assistant_handoffdelete_assistant_handofflist_filesread_filegrep_fileswrite_fileedit_filemove_filearchive_filelist_file_versionspromote_file_versionlist_skillsget_skillcreate_skillupdate_skilldelete_skillassign_skill_to_assistantremove_skill_from_assistantlist_agent_resourcesstart_batch_taskget_batch_taskcontrol_batch_task
adlyse-admin
adlyse-all
  1. Overview
  2. adlyse-workflows

list_authoring_resources

List the org-scoped resources that workflow node fields reference. Call this before authoring nodes so you use real ids instead of guessing: llm nodes need an llm_model, tool_call nodes need a tool id/handle, knowledge_base nodes need knowledge-base ids, assistant nodes need an assistant id, node_credentials values must be credential account ids, and data_table_enrichment triggers need a data table id.

Parameters#

NameTypeRequiredDefaultDescription
resource_typestringnoallOne of "llm_models", "tools", "knowledge_bases", "assistants", "credential_accounts", "slack_workspaces", "mcp_servers", "data_tables", "event_types", "integration_triggers", "integrations". Pass a group to keep the response focused.
tool_handlestringno—Exact tool handle, such as slack.send_message. Requires resource_type="tools"; includes that tool’s registered parameter_schema and output_schema.

Returns#

A dictionary with one key per requested group, each a list of {id, name, …} entries. Metadata only — no secrets. Targeted tool lookups include argument and output schemas.

json
{
  "llm_models": [{ "id": "claude-fable-5", "name": "Claude Fable 5" }],
  "tools": [{ "id": "tool_abc", "name": "Perplexity Search" }],
  "credential_accounts": [{ "id": "credacct_123", "name": "Acme Google Ads" }]
}

Installed Slack apps#

For a new Slack node, prefer a configured installation from resource_type="slack_workspaces". Set its id on data.slack_workspace_id and leave that node’s node_credentials entry unset. Workspace ids and account ids are different credential sources. Preserve an existing bot-token selection when editing unless the user asks to switch.

Fetch resource_type="tools", tool_handle="slack.send_message" for the exact argument names before filling data.parameters.

Errors#

error_typeWhen
auth_errorMissing / invalid / revoked API key
invalid_inputUnknown resource_type, or tool_handle without resource_type="tools"

See also#

  • get_workflow_schema — which node data fields take these ids
  • create_workflow — where the ids get used
Previousdelete_releaseNextlist_tables