The Asana integration converts triggered Remindax reminders into Asana tasks routed to the right workspace, project, section, and assignee — with the item's title, dates, contacts, and a direct link back to Remindax. The toggle is per-reminder, so you choose which items become Asana follow-up work.

What it does

When an enabled reminder triggers, Remindax creates a new Asana task. The task lands on the workspace, project, section, and assignee you configured — turning "we were reminded" into "someone owns the follow-up." Once created, the task is yours to manage in Asana.

What's on each Asana task

  • Task name — built from a customisable template using item placeholders (e.g. Renew: {item_title} – expires {date}).
  • Due date — by default the reminder's expiry or due date; an offset (e.g. 7 days earlier) can be added.
  • Description — item title, expiry/due date, company, department, status, reminder details, contacts, public custom fields, and a direct link to the Remindax item.
  • Assignee — the default assignee you set, overridable per reminder.
  • Project & section — the destination project and (optional) section.

Before you start

  • You're an Administrator in Remindax.
  • You have access to the Asana workspace, project, and section you want tasks to land in.
  • The assignee you'll set as default is a member of the chosen Asana project.

Connect Asana

  1. Go to Settings → Integrations → Asana.
  2. Click Connect Asana and authorise via Asana's OAuth screen.
  3. Choose the default workspace, project, and (optional) section.
  4. Set the default assignee.
  5. Configure the task name template and date offset.
  6. Save. Status switches to Connected.

Enable Asana on a reminder

  1. Open a reminder.
  2. Toggle Create Asana task.
  3. (Optional) Override the workspace, project, section, assignee, or due-date offset for this specific reminder.
  4. Save. When the reminder triggers, a new Asana task is created.

Task name placeholders

Customise task titles with item details:

  • {item_title} — the reminder title.
  • {date} — the expiry / due date.
  • {company} — the Remindax company.
  • {department} — the assigned department.
  • {status} — the reminder status.
  • {reminder_type} — Expiration, Due Date, Appointment, etc.

Example: Renew: {item_title} for {company} – {date} → "Renew: Office insurance for Acme Ltd – 2026-12-15".

How updates work

  • New trigger → a new Asana task is created.
  • Reminder edited after the task exists → Remindax does not update or delete the previously-created Asana task. Edit the task directly in Asana.
  • Reminder deleted → the Asana task is not removed. Close or delete it in Asana if it's no longer relevant.
  • Task completed or reassigned in Asana → does not change Remindax. Update the reminder in Remindax separately if needed.

If you need a fresh task after editing a reminder, toggle the option off and on again, or fire the next sequence step.

Disconnect

  1. Go to Settings → Integrations → Asana and click Disconnect.
  2. New tasks stop being created.
  3. To fully revoke access, also remove Remindax from Asana → Profile Settings → Apps.

Security & privacy

  • Authentication is via Asana OAuth. Remindax never sees your Asana password.
  • Granted scopes are limited to the workspace, project, and assignee data needed to create tasks.
  • OAuth tokens are encrypted at rest.
  • Remindax does not read existing Asana tasks or other projects.

Common use cases

  • Contract and vendor agreement renewals routed to a "Renewals" project, assigned to the contract owner.
  • Employee certification expirations into an HR project section.
  • Business licenses and permits into a Compliance project for the operations team.
  • Asset maintenance deadlines into a Facilities or Fleet project.

Edge cases & gotchas

  • Tasks aren't auto-cleaned. Once a task is created, Remindax doesn't touch it again. Manage completion and deletion in Asana.
  • One task per triggered step. A multi-step sequence with Asana enabled on each step will produce multiple tasks. Limit Asana to the steps that genuinely need follow-up ownership.
  • Default assignee must be in the project. If the assignee isn't a member of the destination project, Asana will reject the task. Add them in Asana first.
  • Per-reminder overrides win. Workspace defaults apply unless the reminder specifies its own workspace/project/section/assignee.
  • Custom fields. Only Remindax custom fields marked as public are written into the Asana task description.

Troubleshooting

  • Task not created → confirm the Create Asana task toggle is on, the destination project still exists, and the assignee is a project member.
  • "Project not found" → the project was archived or moved. Pick a new destination in Settings → Integrations → Asana.
  • "Permission denied" → the connected Asana account no longer has access. Reconnect with an account that does.
  • Wrong due date → check the date offset in the integration settings (or the per-reminder override).

Related questions

  • Will every reminder become an Asana task? No — only reminders with the Create Asana task toggle on.
  • What if I edit a reminder after the task was created? The existing Asana task isn't updated. Edit it in Asana, or fire a new trigger to create a fresh task.
  • Can different reminders use different projects? Yes. Each reminder can override workspace, project, section, and assignee.
  • Will completing the Asana task update Remindax? No. Asana tasks are follow-up work; the reminder status in Remindax is independent.
  • Where does the link in the Asana task go? Back to the original reminder in Remindax, so the task owner can open the source record.

Related articles

Google Calendar integration · Trello integration · Slack integration · Notifications & sequences