Integrations and API
Open Developer in your account and use your API credentials to authenticate server-side requests. The documentation provides the base URL, required fields and response examples for each product.
Start with one workflow, such as sending a transactional message or creating a contact. Keep the API key on your server and validate the request before connecting it to live customer actions.
Use the REST API when your application needs structured messaging, contacts, rewards or other product operations. Use SMTP when your application or website already has an SMTP email configuration. Use SMPP for an SMS integration designed around that protocol.
Choose the interface your application can operate reliably and use the corresponding Yournotify setup guide.
Webhooks send event information from Yournotify to a destination URL in your application. They help you react to supported contact, campaign or reward events without relying only on manual checks.
Open Developer Webhooks, configure your destination and select the event modules you need. Use the available test action to inspect a sample event at your endpoint before relying on it in a live workflow.
Yes. Yournotify has a dedicated ChatGPT integration. Connect your account through the integration flow, then use the supported tools to work with your Yournotify data and workflows from ChatGPT.
The integration page explains the connection and shows the product experience.
Open the integration library to see the listed connections and their current status. Choose the tool you want to connect and follow its dedicated setup instructions.
For a workflow that needs custom mapping or a connection outside the standard setup, share the source system, fields and intended action with our team.
Open the SMTP tab in the Yournotify WordPress plugin and enter the connection settings required for your account. Choose the sender details your website should use for outgoing email.
Save the settings and use a controlled test to confirm that the website can send successfully. Check the destination inbox and the relevant delivery record before relying on the setup for customer notifications.
Use an SMPP client in your Java application to connect your SMS system to Yournotify. Prepare the connection details supplied for your account and a configured SMS sender.
- Open the SMPP integration guide and obtain your account host, port and bind credentials.
- Configure the client connection and bind mode required by your integration.
- Prepare the destination telephone number, sender and message with the correct encoding.
- Submit a controlled test message and record the returned message identifier.
- Handle delivery receipts, errors and reconnects in your application before increasing volume.
Use an SMPP client in your Node.js application to connect your SMS system to Yournotify. Prepare the connection details supplied for your account and a configured SMS sender.
- Open the SMPP integration guide and obtain your account host, port and bind credentials.
- Configure the client connection and bind mode required by your integration.
- Prepare the destination telephone number, sender and message with the correct encoding.
- Submit a controlled test message and record the returned message identifier.
- Handle delivery receipts, errors and reconnects in your application before increasing volume.
Use an SMPP client in your PHP application to connect your SMS system to Yournotify. Prepare the connection details supplied for your account and a configured SMS sender.
- Open the SMPP integration guide and obtain your account host, port and bind credentials.
- Configure the client connection and bind mode required by your integration.
- Prepare the destination telephone number, sender and message with the correct encoding.
- Submit a controlled test message and record the returned message identifier.
- Handle delivery receipts, errors and reconnects in your application before increasing volume.
Use an SMPP client in your Python application to connect your SMS system to Yournotify. Prepare the connection details supplied for your account and a configured SMS sender.
- Open the SMPP integration guide and obtain your account host, port and bind credentials.
- Configure the client connection and bind mode required by your integration.
- Prepare the destination telephone number, sender and message with the correct encoding.
- Submit a controlled test message and record the returned message identifier.
- Handle delivery receipts, errors and reconnects in your application before increasing volume.
Configure your JavaScript mail client with the SMTP connection details from your Yournotify account. This lets an application that supports SMTP send email through your configured Yournotify sender.
- Prepare a verified email sending identity.
- Open the SMTP integration setup and copy the host, port, username, password and encryption settings.
- Store the credentials in your server configuration and apply them to your mail client.
- Set the From address, recipient, subject and message content.
- Send a controlled test and check the application result and email delivery record.
Configure your PHP mail client with the SMTP connection details from your Yournotify account. This lets an application that supports SMTP send email through your configured Yournotify sender.
- Prepare a verified email sending identity.
- Open the SMTP integration setup and copy the host, port, username, password and encryption settings.
- Store the credentials in your server configuration and apply them to your mail client.
- Set the From address, recipient, subject and message content.
- Send a controlled test and check the application result and email delivery record.
Configure your Python mail client with the SMTP connection details from your Yournotify account. This lets an application that supports SMTP send email through your configured Yournotify sender.
- Prepare a verified email sending identity.
- Open the SMTP integration setup and copy the host, port, username, password and encryption settings.
- Store the credentials in your server configuration and apply them to your mail client.
- Set the From address, recipient, subject and message content.
- Send a controlled test and check the application result and email delivery record.
Configure your Ruby mail client with the SMTP connection details from your Yournotify account. This lets an application that supports SMTP send email through your configured Yournotify sender.
- Prepare a verified email sending identity.
- Open the SMTP integration setup and copy the host, port, username, password and encryption settings.
- Store the credentials in your server configuration and apply them to your mail client.
- Set the From address, recipient, subject and message content.
- Send a controlled test and check the application result and email delivery record.
Start with a Meta Business account connected to the Instagram professional account. In Meta for Developers, create or select an app, add the Instagram Graph API permissions you need, and generate a long-lived access token for the account you want to read.
In Yournotify, enter the Instagram Graph API or your approved reporting endpoint as the Endpoint URL, choose Bearer auth, paste the access token, set List Path to the array that contains records, then map the returned fields to Yournotify contacts or lifecycle attributes.
Click Test first. If the response is valid, Save the integration and run Sync Now. If Test fails, confirm the token has the right Instagram permissions, the account is professional, and the endpoint returns JSON.
Use Meta for Developers to create or select an app, connect the Facebook Page or business asset, request the permissions required for the data you want, and generate a page or system-user access token.
Enter the Facebook Graph API endpoint or your approved data endpoint, use Bearer auth for Meta tokens, set the List Path to the response array, and map the response fields to Yournotify contact fields.
If Test fails, check token expiry, app mode, granted permissions, page ownership, endpoint version, and whether the endpoint returns a JSON list at the List Path you configured.
Create an app in the LinkedIn Developer portal, associate it with the correct company page, configure OAuth redirect settings if needed, request the required Marketing or organization permissions, and generate an access token.
Enter the LinkedIn API endpoint or your middleware endpoint, choose Bearer auth, paste the access token, set the List Path to the returned array, and map fields such as name, email, company, campaign, or engagement attributes.
Some LinkedIn APIs require approved products and strict permission review. If direct API access is limited, use a backend endpoint you control to fetch and normalize LinkedIn data before Yournotify syncs it.
Click Connect Google from the Google Sheets integration page, complete Google consent, then return to Yournotify and choose the spreadsheet and sheet tab you want to sync.
Use the first row as column headers and keep one contact or event per row. Include stable columns for name, email, telephone, and any custom fields you want to store as attributes.
Map the sheet columns, choose the target list, Save the integration, then run Sync Now. Review Recent Sync Runs for created, updated, skipped, and error rows.
Use a HubSpot Private App token for simple setup, or connect OAuth when your workspace has HubSpot OAuth configured. In HubSpot, grant CRM object read scopes for the records you want to sync.
Start with firstname, lastname, email, phone, company, lifecycle stage, and any properties used for segmentation. Add those property names in the Properties CSV field.
Click Test after entering the token and properties. If it fails, confirm the private app scopes, token value, and whether the properties exist in HubSpot.
Create a Zoho API client in the Zoho API Console, configure the redirect URI shown in Yournotify, and connect OAuth from the integration page when the server OAuth settings are available.
Choose the module you want to sync, usually Leads or Contacts, then map Full_Name, Email, Phone, Company, owner, status, and any custom fields used in campaigns.
Confirm the Zoho data center, OAuth client settings, redirect URI, granted scopes, and selected module before running Sync Now.
Use your Odoo base URL, database name, username, and API key or password from the Odoo user preferences. The account should have read access to contacts or the model you want to sync.
Enter the Odoo URL and credentials, choose the model or endpoint that returns contacts, then map name, email, phone, company, tags, and lifecycle fields.
Check the database name, user access rights, API key, SSL URL, and whether the selected model has readable records if Test fails.
Create a Personal Access Token in Airtable, grant access to the required base, then copy the Base ID and table name from Airtable.
Paste the Personal Access Token, Base ID, and table name. Then map Airtable columns to name, email, telephone, and custom attribute fields.
If Test fails, confirm the token can access the base, the Base ID starts with app, the table name is exact, and the mapped columns exist.
In Pipedrive, open Personal preferences, go to API, and copy your API token. Use an account that can read persons, organizations, and deals needed for sync.
Paste the API token, add the company domain when needed, and map person fields such as name, email, phone, organization, deal stage, and owner.
Click Test and confirm Yournotify can read sample records. If it fails, check the token, company domain, and user permissions.
In Paystack Dashboard, open Settings, API Keys and Webhooks, then copy the Secret Key for the environment you want to sync. Use live keys only for production data.
Start with customers, transactions, subscriptions, and metadata that help segment payment activity. Map email, customer name, phone, amount, status, plan, and transaction dates.
Confirm live versus test mode, secret key permissions, API base URL if customized, and whether customer records include the fields you mapped before Sync Now.
In Flutterwave Dashboard, open Settings, API Keys, then copy the Secret Key for test or live mode. Use a key with access to customers and transactions.
Map customer name, email, phone, transaction amount, currency, status, payment type, and created date so campaigns can target payment behavior.
Check whether the key is live or test, whether the endpoint is reachable, and whether the returned JSON path matches the List Path in Yournotify.
Create an app in Xero Developer, add the redirect URI shown in Yournotify, and connect OAuth when your workspace has Xero OAuth configured.
Use contacts, invoices, payment state, due dates, and account status fields to support billing reminders and lifecycle campaigns.
Confirm the Xero tenant, OAuth scopes, redirect URI, token status, and the endpoint or list path configured in Yournotify if it fails.
Use Sage developer credentials or a Sage-connected middleware endpoint that exposes customers, invoices, or accounts as JSON.
Enter the endpoint URL, choose the correct auth type, paste the access token or API key, set the List Path, and map customer and billing fields.
Use middleware when your Sage edition needs custom authentication, tenant selection, or transformation before records can be synced into Yournotify.
Use your Moniepoint business or developer dashboard to obtain API credentials, or expose a secure middleware endpoint if your account uses a custom reporting flow.
Sync customers, terminals, payment references, transaction amounts, status, and timestamps for operational and billing messages.
Enter the endpoint and API key, set the List Path to the records array, then click Test. Confirm the response contains the fields used in your mappings.
Prepare the host, port, database, username, password, SSL requirement, and the table or view that returns contacts or lifecycle records.
Use a table or view with stable identifiers plus name, email, phone, timestamps, status fields, and any campaign segmentation attributes.
Use a read-only database user, restrict network access, enable SSL where possible, and avoid exposing sensitive columns that are not needed for messaging.
Prepare host, port, database name, username, password, SSL setting, and the table or view that contains contacts or customer events.
Map a stable identifier, name, email, telephone, customer status, dates, and custom attributes that support segmentation.
Use a read-only user, start with a small table or view, click Test, then Save and Sync Now after verifying the returned records.
Prepare a MongoDB connection string, database name, collection name, and a read-only user. Use Atlas network access rules if the database is hosted on MongoDB Atlas.
Map name, email, telephone, status, timestamps, and nested attributes needed for segmentation. Use predictable field names for nested values.
Check the connection string, database and collection names, IP allowlist, user permissions, and whether the documents contain the mapped fields if Test fails.