Create Entry
Create new Gravity Forms entries programmatically.
Overview
The Create Entry action creates a new entry in a Gravity Forms form. This is useful for importing data, creating entries from other systems, or generating entries based on triggers.
Configuration
Required Fields
| Field | Type | Description |
|---|
| Form | select | Target form |
| Fields | object | Field values by ID |
Optional Fields
| Field | Type | Description |
|---|
| Created By | integer | User ID |
| Date Created | date | Entry date |
| Status | select | active, spam, trash |
| Source URL | string | Originating URL |
| IP Address | string | IP address |
Mapping Fields
Map trigger data to form field IDs:
Form: Contact Form (ID: 1)
Fields:
1: {{Trigger.name}} # Name field
2: {{Trigger.email}} # Email field
3: {{Trigger.phone}} # Phone field
4: {{Trigger.message}} # Message field
Example Configurations
Import from CRM
Form: Lead Capture
Fields:
1: {{Trigger.crm_name}}
2: {{Trigger.crm_email}}
3: {{Trigger.crm_company}}
4: {{Trigger.crm_phone}}
Created By: 1
Order to Form Entry
Form: Order Records
Fields:
1: {{Trigger.order_number}}
2: {{Trigger.billing.email}}
3: {{Trigger.billing.first_name}} {{Trigger.billing.last_name}}
4: {{Trigger.total}}
Webhook to Entry
Form: API Submissions
Fields:
1: {{Trigger.webhook_name}}
2: {{Trigger.webhook_email}}
3: {{Trigger.webhook_data}}
Source URL: {{Trigger.webhook_source}}
Field Type Mapping
| Gravity Forms Field | Value Format |
|---|
| Single Line Text | String |
| Email | Email string |
| Number | Numeric string |
| Name (prefix.first.last) | Object or combined |
| Address | Object with subfields |
| Checkbox | Comma-separated |
| Select/Radio | Selected value |
| Date | YYYY-MM-DD |
Output Data
| Variable | Type | Description |
|---|
{{Action.entry_id}} | integer | Created entry ID |
{{Action.form_id}} | integer | Form ID |
Common Workflows
Data Migration
- Trigger: External system event
- Action: Create Entry
- Map all fields from source
Backup System
- Trigger: Order Created
- Action: Create Entry
- Store order data as form entry
- Trigger: Form A submitted
- Action: Create Entry (Form B)
Best Practices
- Verify field IDs before mapping
- Handle required fields appropriately
- Test with sample data first
- Log creation for tracking