Tables hold structured data inside Sydekyks. A mission can save results, look up an existing record, and react when a record changes.

​
Why they exist

Missions often need to remember which leads you already contacted or which invoices still need review. A table keeps that state between runs.

Fields and records

Five field types, and how data gets in.

Use in missions

Read, write, and start missions when data changes.

Import and export

Bring a CSV in, take your data out.

​
A shape that comes up often

  1. A mission collects something, such as an inbound lead, and writes a record.
  2. A new record trigger starts a second mission to enrich or route it.
  3. The second mission updates the record with its result.
The table lets those missions share state. Check feature availability before planning optional assistant features around it.