Flow actions
NumberForge ships two invocable actions for Flow:
- NF Process Phone: validate, format, and optionally enrich one phone value
- NF Find Phone Numbers: extract phone numbers from text
Both use the standard Flow action editor and scalar inputs (not collection-shaped phone lists on the request).
When to use what
Section titled “When to use what”| Approach | Best for |
|---|---|
| Record-save processing (NumberForge Configuration) | Every Contact/Lead/Account save with consistent rules |
| NF Process Phone | Screen flows, platform events, integration paths, one-off transforms |
| NF Find Phone Numbers | Parsing Notes, email bodies, or chatter text in Flow |
Apex NF.* | Custom batch, REST, or logic Flow cannot express. API Reference |
Shared behavior
Section titled “Shared behavior”- Status strings match Key concepts:
VALID,INVALID,NEEDS_REGION,EMPTY(Process Phone only). - Default Region and Output Format on Process Phone fall back to org defaults when blank.
- Enrichment uses offline metadata (see Performance).
Permissions
Section titled “Permissions”Flow runs in the running user’s context. Ensure profiles can execute the actions and read/write referenced fields.