1.6.6 — Explicit library exports, clearer Job outcomes and browser collaboration

​

Highlights

• Define JavaScript and TypeScript library APIs with named exports and a permanent default element.
• Investigate terminal Job outcomes, inspect every attempt and start another manual retry after earlier work has settled.
• Choose shallow override, recursive override or replacement when supplying automation input.
• Search trigger names with consistent contains matching across resource filters.
• Let public web reads fall back to an isolated browser when an ordinary HTTP response is insufficient.
• Follow an Assistant browser live and take private control when a workflow needs human input.
• Transfer HTTP content directly to or from authorized Storage files with consistent request and response handling.

​

In detail

const response = await api.httpCall(
  { url: 'https://example.com/status', method: 'GET' },
  { responseType: 'json', proxy: true, timeout: 15000 },
);
if (response.status !== 200) throw new Error('Status request failed');
return response.data;

const response = await api.httpCall(
  { url: 'https://example.com/report.csv', method: 'GET' },
  { responseType: 'storage', proxy: true,
    target: { name: 'report.csv', contentTypeHint: 'text/csv', computeStats: 'sync' } },
);
if (!response.storage) throw new Error('Report was not stored');
return response.storage.entry;

const response = await api.httpCall(
  { url: 'https://example.com/import', method: 'POST' },
  { requestType: 'storage', proxy: true,
    source: { storageEntryId: api.input().body.storageEntryId }, timeout: 60000 },
);
if (response.status < 200 || response.status >= 300) throw new Error('Import failed');
return { status: response.status };

​

Also in this release

• Account verification, invitations and other platform emails share consistent structure, sender presentation, action links and plain-text alternatives. Verification and invitation links remain valid for 30 days; password-reset expiry follows the authentication provider’s existing policy.
• Assistant browser continuation and activity retain the relevant interaction context while private control is active. Runtime guidance distinguishes public page reads from interactive sessions and individual Job errors from terminal execution outcomes.

​

Related guides

• Components
• Jobs
• Events
• Terminals
• Storage

​

Continue through the releases