Encode URI Components (Utility)
Encode → Encode URI Components (Utility)
URL-encodes a string for safe use in query parameters and URL paths.
Input
What it needs.
Map each field to a column in your table. Optional fields can stay empty.
original_valueThe text string to be URI encoded.text
When to use this.
URL-encodes a string for safe use in query parameters and URL paths.
Output
What it returns.
Every field this action writes back to the row. Click a line to expand nested objects.
encoded_valueEncoded Valuetextoriginal_valueOriginal Valuetext
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
Workflow
A real example.
Trigger → encode uri components (utility) → enrich → push to your CRM. You set it up once; after that it runs without you.
Built for
Who runs this.
Reliability
Throughput & reliability.
How fast it drains a table, and what happens when the upstream provider has a bad day.
- Per-minute limit300 / min
- Per-day limit10,000 / day
- RetriesAutomatic w/ backoff
- Failed lookupsZero credits
FAQ.
Is this real-time?
Mostly. Fast actions fill the cell in a few seconds. Long-running ones run in the background and write back to the row when they finish, so you can close the tab.
Do I get charged on failure?
No. A failed lookup costs zero credits. When a provider misses or times out, the waterfall moves to the next one and you only pay for the match you actually got.
Do I have to run it row by row?
No. Run it on one cell, on a selection, on the whole table, or on a schedule. Same action either way.
What CRMs can I push results to?
HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.
Run Encode URI Components (Utility) in 60 seconds.
Connect the account, drop the action on a column, run it on your rows.