Skip to content
Notis

Retrieve Campayn contact details with a request

When a teammate has a contact id, let them request the Campayn record without a separate manual lookup.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Get Contact

Tool to retrieve a specific contact by id. use when you need to fetch full contact details after confirming the contact id.

Why this helps

Looking up one contact can interrupt the work at hand when the record id is already known.

  • Retrieve a specific contact by its known id.
  • Make one contact lookup easy to request.
  • Return the details through the run report.

Setup

Build it in a few focused steps.

  • 1Connect Campayn once in the Notis portal.
  • 2Create an automation in the portal or tell Notis from any channel.
  • 3In one instruction, say to retrieve the Campayn contact for the id supplied with the request.
  • 4Pick a webhook trigger and provide its request URL to the people or system that will call it.
  • 5Choose a report channel, then test with one real contact id.

Questions about this workflow

What does the webhook request need?

It needs the Campayn contact id because the action retrieves one specific contact by id.

Does the workflow change contact data?

No. Get Contact retrieves the contact details.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Campayn. A trigger fires from one place; an action lands in another.

Jira triggers

Campayn actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Contact

Tool to create a new contact in a specific list. use when you need to add a contact after gathering details.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Contact

Tool to delete a specific contact. use when you need to remove a contact permanently after confirming it should be deleted. example: "delete contact 123".

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Delete List

Tool to delete a specific contact list. use when cleaning up unused lists after confirming they are no longer needed. example: "delete list 123".

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Delete webform

Tool to delete a specific webform. use when removing outdated or unnecessary webforms after confirming they are no longer needed. example: "delete webform 123".

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Get Contact

Tool to retrieve a specific contact by id. use when you need to fetch full contact details after confirming the contact id.

ActionInstant

Get Contacts

Tool to retrieve all contacts in a specified list. use when you need to fetch list contacts after confirming list id.

ActionInstant

Get List

Tool to retrieve a specific contact list by id. use when you need to fetch list details like name, tags, and contact count after knowing the list id.

ActionInstant

Get Lists

Tool to retrieve all contact lists. use when you need to fetch available lists before performing list-specific actions. example prompt: "list all my contact lists".

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Campayn, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Campayn.