Actions182
- Address Block Actions
- Audit Log Actions
- Auth Profile: LDAP Actions
- Auth Profile: OIDC Actions
- Auth Profile: SAML Actions
- CDC Application Actions
- CDC Destination: HTTP Actions
- CDC Destination: Splunk Actions
- CDC Destination: Syslog Actions
- CDC Host Actions
- Custom API Request Actions
- DFP Service Actions
- DHCP Fingerprint Actions
- DHCP Lease Actions
- DNS Event Actions
- DNS Record Actions
- DNS Zone Actions
- Endpoint Device Group Actions
- Endpoint Roaming Device Actions
- Endpoint VPN Profile Actions
- Fixed Address Actions
- Global Search Actions
- Identity: Compartment Actions
- Identity: Group Actions
- Identity: User Actions
- Infrastructure Host Actions
- Infrastructure Service Actions
- IP Address Actions
- IP Space Actions
- IPAM Range Actions
- Location Actions
- Lookalike Domain Actions
- Lookalike Target Actions
- NIOS Custom API Request Actions
- NIOS WAPI Object Actions
- NTP Service Config Actions
- Redirect: Custom Redirect Actions
- Service Log Actions
- SOC Insight Actions
- Subnet Actions
- TD Access Code Actions
- TD Application Filter Actions
- TD Category Filter Actions
- TD Internal Domain List Actions
- TD Named List Actions
- TD Scheduled Report Actions
- TIDE Batch Actions
- TIDE Dossier Lookup Actions
- TIDE Threat Actions
Endpoint VPN Profile → Create
AI-generatedSummary
Creates a new BloxOne Endpoint VPN profile by POSTing a JSON body to the Infoblox Portal API endpoint /api/atcep/v1/vpn_profiles.
Inputs
- Fields (dataFields) (required) — Resource mapper listing writable fields for a VPN profile, loaded from the Infoblox Atcep API spec (read-only fields and id are skipped; required fields listed first). Falls back to empty if the schema can't be loaded.
- JSON Body (jsonBody) — Extra request body as JSON, merged over the mapped fields (JSON values win on conflicts). Use for fields missing from the schema.
- Query Parameters — Optional name/value pairs appended to the request query string.
Output shape
One output item per input item, containing the API's response for the created VPN profile (typically the new record as JSON).
Non-object responses are wrapped as { result: value }. With Continue On Fail enabled, errors are returned as { error: message } for that item. Requires Infoblox CSP API credentials.
Examples
Example 1: Create a VPN profile from mapped fields
Resource: Endpoint VPN Profile, Operation: Create; fill required fields (e.g. name) in the Fields mapper.
Example 2: Create a profile using a raw payload from a previous node
Leave mapper fields empty and set JSON Body to an expression like {{ JSON.stringify($json.profile) }}.