What You Can Do
Content templates
Draft and update templates for any Airship channel: email, SMS, open channel, app (mobile push), web push, and Message Center. Preview rendered templates inline before sending.
Sending and scheduling
Send notifications immediately or schedule for a future time. View, update, or cancel existing schedules. Target named users, channels, segments, static lists, or audience expressions.
Audience management
Inspect and update named users and individual channels. Manage static lists and read existing segments. Look up which channels a user is reachable on before drafting a send.
Pipelines
View and manage Airship pipelines — event-triggered automations.
Prerequisites
- Admin access to your Airship project to create credentials
- Your Airship project’s regional API host (North America or Europe)
- A Gradial organization Administrator role to complete setup
How to Connect
Get your authentication details from Airship
Airship supports three auth methods. Choose the one your security team prefers:OAuth Client Credentials (recommended)
- Sign in to Airship as a project admin and open OAuth Clients in your project settings.
- Create a dedicated client for Gradial, scoped to the operations the team needs (content templates, schedules, audiences, sends).
- Copy the App Key, Client ID, and Client Secret.
- Note your region (NA or EU).
- Open your Airship project’s Settings → APIs & Integrations.
- Copy the App Key and Master Secret.
appKey:masterSecret token elsewhere in your tooling, paste it into the API-key-header dialog with the prefix Basic.Add the integration in Gradial
- In Gradial, go to Settings → Integrations.
- Find Airship and click + Add.
- Fill in the connection details:
| Field | Value |
|---|---|
| Integration Name | A display name (e.g., Acme Marketing — Production) |
| Airship API Base URL | https://go.urbanairship.com (NA) or https://go.airship.eu (EU) |
| Authentication Method | OAuth Client Credentials, App Key + Master Secret, or Base64 Token |
| Credentials | From step 2 |
- Click Save. Gradial validates the credentials and region before the integration goes live.
How It Fits Into Broader Workflows
| Use case | How to use it |
|---|---|
| Multi-channel campaign moment | Draft email, push, and in-app templates side-by-side, preview inline, and schedule each channel’s send for the same launch time |
| Audience targeting | Gradial discovers segments and audiences so the team can confirm targeting before sending — no juggling segment IDs by hand |
| One-off notifications | Find a named user or channel, draft the message, and send immediately or schedule |
| Static list maintenance | Look up a current static list, update membership, and confirm the change before the next scheduled send |
- Ask Gradial to draft an email template for the campaign — subject, preheader, and body copy.
- Have Gradial draft a matching mobile push template and a web push template.
- Preview all three inline in the thread to QA the creative.
- Schedule each send for the same launch time, targeting the right segment or static list.
- Open the Airship artifact for each template to monitor in the Airship dashboard.
Good to Know
- Region awareness: NA and EU Airship projects sit on different hostnames. The connection dialog auto-switches the API base URL when the region changes.
- Sends never auto-retry: writes (sending a notification, creating a schedule, mutating audiences) intentionally do not retry on failure. A failed send is reported back and stops — the agent never silently double-sends.
- Inline previews are sanitized: the preview proxy strips remote fonts, inline scripts, and unsafe CSS. It preserves inline data URIs and inline blobs so legitimate creative still previews correctly.
- OAuth credential rotation: when rotating Airship OAuth credentials, Gradial preserves project-level config across the rotation. The old cached token can serve requests until its natural expiry (up to ~60 minutes), so plan for that window for security-motivated rotations.