SendMobileForm

post

https://{environment}.origamirisk.com/OrigamiApi/api/v2/Actions/Queue/SendMobileForm/{domain}/{recordId}

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Overview

The SendMobileForm action sends a mobile-optimized form to a specified recipient via SMS text message. The form is designed to be easily completed on mobile devices and allows external users to submit data back to the Origami system without requiring system access or login credentials.

How It Works

When executed, this action generates a secure, time-limited link to a mobile form and sends it via SMS to the specified phone number. The recipient receives a text message containing the link and can tap to open the form on their mobile device. Once completed and submitted, the form data is captured in the Origami system and associated with the triggering record. This enables organizations to quickly collect information from external parties like claimants, witnesses, or vendors directly through their mobile phones.

Typical Use Cases

Organizations commonly use mobile forms for accident scene data collection, property damage assessments, witness statements, vendor completion confirmations, customer satisfaction surveys, and any scenario where quick, mobile-friendly data capture from external parties improves workflow efficiency and response times.

Path Params

domain

string

required

The SendMobileForm action can operate on any domain where mobile data collection makes business sense. Common use cases include sending forms from Claims (to collect accident details from claimants), Policies (to gather application information from insureds), Assets (for inspection reports), or Work Orders (for completion confirmations). The action uses the triggering record (specified by domainName and domainKey) to provide context for the mobile form and to associate any submitted responses with the appropriate business record.

recordId

integer

required

The recordId is the primary key (ID) of the specific record that triggers the mobile form and serves as the anchor for the entire interaction. This record:

Triggered the action - The event occurred on this record (e.g., Claim ID 12345 was updated to "Under Investigation" status)
Provides form context - The mobile form can display information from this record to give recipients context about what they're responding to (e.g., "Please provide details about Claim #12345")
Receives the response data - When the mobile form is completed and submitted, the response data is associated with and stored against this specific record
Enables form tag resolution - Dynamic content in the SMS message and mobile form (like {Claim.ClaimNumber} or {Policy.InsuredName}) is resolved using data from this record

Example:

When Claim #12345 status changes to "Investigating":

domainName: "Claim"
domainKey: 12345 (the specific claim being investigated)
SMS sent with context: "Please complete this form regarding Claim #12345"
Mobile form displays relevant claim details for reference
When submitted, the form response is linked to Claim #12345
Response data appears in Claim #12345's record for future reference

Body Params

parameters

object

required

Response

Overview

How It Works

Typical Use Cases

200