# Best way to translate text-based records? **URL:** \ **Category:** Automations and Integrations\ **Created:** [March 29, 2023, 6:24pm UTC](https://air.tableforums.com/t/best-way-to-translate-text-based-records/479 "2023-03-29T18:24:58Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![bfrench](https://yyz1.discourse-cdn.com/flex029/user_avatar/air.tableforums.com/bfrench/32/46_2.png) [@bfrench](https://air.tableforums.com/u/bfrench)\ **Post date:** [March 29, 2023, 9:54pm UTC](https://air.tableforums.com/t/best-way-to-translate-text-based-records/479/4 "2023-03-29T21:54:09Z")
Tana is very powerful. Getting into the alpha group has proven difficult. Took me 6 months. And then, there’s the AI testpilots group. That took another three months to get in. Hopefully they are onboarding faster now. But, in the meantime, there’s nothing about these processes that cannot be done in Airtable using its current scripting environment and OpenAI’s APIs. While Tana is probably way ahead of Airtable in terms of seamless LLM integration, it will not likely be released for another year perhaps. Airtable is ready now to use LLs to change pretty much everything and only limited to the imagination of developers and domain experts. I’ve written about some of the ideas [here](https://air.tableforums.com/t/gpt-plugins-existential-no-code-threat/450), and [here](https://air.tableforums.com/t/ai-copilots-everywhere-gpts-trillion-dollar-economy/419), and [here](https://air.tableforums.com/t/no-code-low-code-and-low-effort-code/155). These are not translation-specific, but they are AGI-specific. In my view - anything that we may have imagined through services related to NLP that existed before June 2022, should be flatly disregarded. AGI has advanced so fast since then that almost every conceptual way to do translations or anything related to NLP is obsolete. --- _[View the full topic](https://air.tableforums.com/t/best-way-to-translate-text-based-records/479)._