$echo '{
< "texts": [
< "Our platform lets you connect a data source, transform records with a visual pipeline builder, and publish the result to any destination without writing code. Most teams get their first pipeline running within an afternoon, and support is available by chat if you get stuck along the way.\\n\\nConnections are managed centrally. Once you authorize a data source, every pipeline in your workspace can reuse that connection, so credentials are entered once and rotated in a single place. We support more than sixty destinations, including data warehouses, spreadsheets, and webhooks, and new destinations are added every month based on customer requests submitted through the roadmap board.\\n\\nPipelines run on a schedule you define, from every five minutes to once a month, or you can trigger a run manually from the dashboard or through the API. Each run produces a detailed log you can inspect later, and failed runs send an alert to the channel you configure, whether that is email, Slack, or a custom webhook endpoint of your choosing.\\n\\nHistorical run data is retained for ninety days on paid plans and seven days on the free plan. You can export any run'\''s input and output as JSON at any time, which is useful for debugging a transform step or for feeding results into another system entirely.\\n\\nRole-based access control lets you decide who can view, edit, or run each pipeline. Workspace owners can invite teammates by email, assign them to one of four roles, and restrict sensitive connections to a specific team. Audit logs record every permission change so you always know who altered access and when.\\n\\nPricing is usage-based and scales with the number of records processed each month rather than the number of pipelines or seats, so you can add as many teammates and workflows as you like without the bill changing. A free plan covers light usage and is a good way to evaluate the product before committing to a paid tier. Enterprise customers can request a fixed-price contract with a dedicated support engineer and a custom data retention window.\\n\\nThe underlying engine retries failed steps automatically using exponential backoff, and it de-duplicates records so a retried run never writes the same row twice to your destination. If a destination is temporarily unreachable, pending records queue safely and resume delivery once the destination comes back online, so a brief outage downstream does not require you to manually replay anything.\\n\\nMonitoring is built into every workspace. A live status page shows the health of each pipeline, the average run duration over the last thirty days, and the volume of records processed per hour. You can set custom thresholds so an alert fires before a slow pipeline turns into a missed deadline, rather than only after something has already broken downstream.\\n\\nMigrating from another tool is usually the first thing new customers ask about. Our import wizard reads an existing pipeline configuration from several competing tools and recreates the equivalent steps automatically, flagging anything it could not translate so you can finish those by hand. Most migrations of a few dozen pipelines are completed within a single working day, including validation against a sample of real production data."
< ]
<}' |
<apify call raional/text-chunker --silent --output-dataset