Hey @Letras Diferentes , since the tool you're using doesn't have a public API, you can still achieve this using Pipefy's native Integrations (iPaaS) or similar platforms like Zapier or Make, all of which support custom code steps that let you implement the text transformation logic directly, without relying on any external tool.
Suggested flow:
- Trigger: Card created or updated in Pipefy
- Code step (JavaScript): Transform the text using a Unicode character map
- Action: Update the card field in Pipefy with the styled text
Code step example (cursive/script style):
const script = {
a:'𝓪', b:'𝓫', c:'𝓬', d:'𝓭', e:'𝓮', f:'𝓯', g:'𝓰', h:'𝓱',
i:'𝓲', j:'𝓳', k:'𝓴', l:'𝓵', m:'𝓶', n:'𝓷', o:'𝓸', p:'𝓹',
q:'𝓺', r:'𝓻', s:'𝓼', t:'𝓽', u:'𝓾', v:'𝓿', w:'𝔀', x:'𝔁',
y:'𝔂', z:'𝔃'
};
const transform = (text) =>
text.split('').map(c => script[c.toLowerCase()] || c).join('');
return { styledText: transform(inputs.originalText) };
Why this approach works well:
- You fully control the transformation logic in the code step
- The result is written back to the card field automatically via Pipefy's native action
- You can easily add other styles (Fraktur, double-struck, fullwidth, etc.) by swapping the character map
That said, while this approach works, it introduces unnecessary complexity and cost, you'd be consuming integration tasks just to perform a text transformation that could simply be done beforehand, outside of Pipefy. A more practical alternative would be to style the text first using your preferred tool or a simple script, and then paste the result directly into the card field. This keeps your workflow lean and avoids unnecessary automation overhead.
